upringjs / swim-hashringLinks
consistent hashring based on swim, for node.js
☆38Updated 5 years ago
Alternatives and similar repositories for swim-hashring
Users that are interested in swim-hashring are comparing it to the libraries listed below
Sorting:
- All the ways for doing requests/streams multiplexing over a single stream☆39Updated 7 years ago
- A base swim node☆15Updated 8 years ago
- PubSub system built on top of UpRing☆18Updated 7 years ago
- Node.js globbing for amqp-like topics☆49Updated last year
- Job Queue in LevelDB☆86Updated 2 years ago
- Superseded by many-level. Multilevel implemented using leveldowns with reconnect support.☆58Updated 7 months ago
- Add a 'ttl' (time-to-live) option to levelup for put() and batch().☆70Updated 2 years ago
- Elect a leader using unix sockets, for node☆20Updated 6 years ago
- Basic http wrapper to call the docker remote api from node☆56Updated 6 years ago
- Route your functions with pattern matching☆12Updated 9 years ago
- A message based router for building distributed systems☆26Updated 8 years ago
- Superseded by rave-level. Open a leveldb handle multiple times.☆146Updated 7 months ago
- Node.js module used for safely running untrusted streaming JavaScript microservices.☆26Updated 8 years ago
- Easily make random-access-storage instances☆76Updated last year
- run your benchmarks as part of your dev flow, for Node.js☆47Updated 8 years ago
- A fault tolerant changes stream for couchdb☆57Updated 2 years ago
- A Raft implementation that focuses on ease of use☆64Updated 8 years ago
- Service discovery in node using ContainerPilot☆27Updated 6 years ago
- RPC library based on net sockets, can work both with tcp sockets and ipc.☆12Updated 7 years ago
- HTTP auth module to require admin page users to be in a Github org☆14Updated 6 years ago
- Zero-overhead asynchronous series/each/map function calls☆69Updated 5 years ago
- Turn a leveldb into one huge object of arbitrary size! Efficiently and atomically update and read parts of it!☆46Updated 4 years ago
- Figure out if your node process is blocked because the CPU is spinning and exit the program with a stack trace if that is the case☆68Updated 6 years ago
- Key Value store on top of Upring.☆10Updated 7 years ago
- Horizontally Scalable EventEmitter powered by a Merkle DAG☆70Updated 9 years ago
- convert a node stream (classic or new) into a pull-stream☆30Updated 4 years ago
- Cache and replay NodeJS streams☆40Updated 5 years ago
- Data classification algorithms☆18Updated 10 years ago
- no longer maintained, sorry!☆196Updated 7 years ago
- Amazon S3 blob-store☆67Updated 3 years ago