Disque vs ZeroMQ: What are the differences?
What is Disque? In-memory, distributed job queue. Disque is an ongoing experiment to build a distributed, in-memory, message broker. Its goal is to capture the essence of the "Redis as a jobs queue" use case, which is usually implemented using blocking list operations, and move it into an ad-hoc, self-contained, scalable, and fault tolerant design, with simple to understand properties and guarantees, but still resembling Redis in terms of simplicity, performance, and implementation as a C non-blocking networked server.
What is ZeroMQ? Fast, lightweight messaging library that allows you to design complex communication system without much effort. The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.
Disque and ZeroMQ can be primarily classified as "Message Queue" tools.
Disque and ZeroMQ are both open source tools. It seems that Disque with 7.37K GitHub stars and 516 forks on GitHub has more adoption than ZeroMQ with 5.33K GitHub stars and 1.57K GitHub forks.
What is Disque?
What is ZeroMQ?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Disque?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Disque?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Disque?
Our platform is based on interconnected services with a custom RPC protocol based on ZeroMQ and inspired by ZeroMQs LPP/MDP protocols.