Distributed application framework
Want to see pretty graphs? Log in now!
npm install culture
|4||downloads in the last month|
|Last Published By|
|Version||0.0.0 last updated 6 months ago|
|Keywords||distributed, zeromq, cluster, message, queue|
Put your application in a petri dish and watch it grow
A service should be able to appear and disappear from within a platform at will and not lose a critical message. Each service will have knowledge of alive services by way of a shared redis node.
- ZeroMQ-based message brokering: pub-sub, req-rep
- optional message persistence
- service location: lookup, announce
- cache layer
- persistence layer
- RESTful router