Deepstream.io
| Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
|---|---|---|---|---|---|---|---|---|---|---|
| Deepstream.io | 7,064 | | 97 | 22 | 2 months ago | 68 | July 24, 2019 | 7 | mit | TypeScript |
| deepstream.io server | ||||||||||
| Hmq | 1,192 | 1 | 11 | 6 days ago | 5 | March 18, 2021 | 53 | apache-2.0 | Go | |
| High performance mqtt broker | ||||||||||
| Lan | 494 | 3 years ago | 2 | December 10, 2015 | mit | JavaScript | ||||
| Internet of Things Server Layer with CoAP, WebSocket, MQTT, HTTP Protocol. | ||||||||||
| Mosquitto Go Auth | 410 | 12 hours ago | 6 | March 11, 2021 | 13 | mit | Go | |||
| Auth plugin for mosquitto. | ||||||||||
| Jaguar | 409 | 54 | 54 | a year ago | 208 | April 09, 2022 | 20 | bsd-3-clause | Dart | |
| Jaguar, a server framework built for speed, simplicity and extensible. ORM, Session, Authentication & Authorization, OAuth | ||||||||||
| Dsock | 197 | 2 years ago | 4 | April 12, 2021 | 1 | mit | Go | |||
| Distributed WebSocket broker | ||||||||||
| Occamy | 196 | 2 years ago | 7 | April 20, 2021 | 9 | mit | Go | |||
| 🖥️ a modern remote desktop proxy written in Go | ||||||||||
| Philote | 161 | 4 years ago | 10 | February 21, 2019 | 1 | other | Go | |||
| Simple, topic-based PUB/SUB WebSocket server. | ||||||||||
| Zwave Js Server | 122 |  | 2 | 20 hours ago | 63 | March 24, 2023 | 3 | apache-2.0 | TypeScript | |
| Huobi | 109 |  | 2 | 1 | 4 years ago | 46 | July 15, 2019 | mit | Python | |
| 火币的行情交易的python实现 | ||||||||||
deepstream - the open realtime server 
deepstream is an open source server inspired by concepts behind financial trading technology. It allows clients and backend services to sync data, send messages and make rpcs at very high speed and scale.
deepstream has three core concepts for enabling realtime application development
- records (realtime document sync)
records are schema-less, persistent documents that can be manipulated and observed. Any change is synchronized with all connected clients and backend processes in milliseconds. Records can reference each other and be arranged in lists to allow modelling of relational data
- events (publish subscribe messaging)
events allow for high performance, many-to-many messaging. deepstream provides topic based routing from sender to subscriber, data serialisation and subscription listening.
- rpcs (request response workflows)
remote procedure calls allow for secure and highly available request response communication. deepstream handles load-balancing, failover, data-transport and message routing.
- security (Authentication and Permissions)
deepstream offers a combination of different authentication mechanisms with a powerful permission-language called Valve that allows you to specify which user can perform which action with which data.
Getting Started:
Community Links
Contributing
deepstream development is a great way to get into building performant Node.js applications, and contributions are always welcome with lots of ❤. Contributing to deepstream is as simple as having Node.js (10+) and TypeScript (3+) installed, cloning the repo and making some changes.
~ » git clone [email protected]:deepstreamIO/deepstream.io.git
~ » cd deepstream.io
~/deepstream.io » git submodule update --init
~/deepstream.io » npm i
~/deepstream.io » npm start
_ _
__| | ___ ___ _ __ ___| |_ _ __ ___ __ _ _ __ ____
/ _` |/ _ \/ _ \ '_ \/ __| __| '__/ _ \/ _` | '_ ` _ \
| (_| | __/ __/ |_) \__ \ |_| | | __/ (_| | | | | | |
\__,_|\___|\___| .__/|___/\__|_| \___|\__,_|_| |_| |_|
|_|
===================== starting =====================
From here you can make your changes, and check the unit tests pass:
~/deepstream.io » npm t
If your changes are substantial you can also run our extensive end-to-end testing framework:
~/deepstream.io » npm run e2e
For power users who want to make sure the binary works, you can run sh scripts/package.sh true. You'll need to download the usual node-gyp build environment for this to work and we only support the latest LTS version to compile. This step is usually not needed though unless your modifying resource files or changing dependencies.
