Disque vs RabbitMQ: What are the differences?
Developers describe Disque as "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. On the other hand, RabbitMQ is detailed as "A messaging broker - an intermediary for messaging". RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
Disque and RabbitMQ can be categorized as "Message Queue" tools.
Disque and RabbitMQ are both open source tools. It seems that Disque with 7.37K GitHub stars and 516 forks on GitHub has more adoption than RabbitMQ with 5.94K GitHub stars and 1.78K GitHub forks.
What is Disque?
What is RabbitMQ?
Want advice about which of these 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?
Sign up to get full access to all the tool integrationsMake informed product decisions
I developed one of the largest queue based medical results delivery systems in the world, 18,000+ queues and still growing over a decade later all using MQSeries, later called Websphere MQ. When I left that company I started using RabbitMQ after doing some research on free offerings.. it works brilliantly and is incredibly flexible from small scale single instance use to large scale multi-server - multi-site architectures.
If you can think in queues then RabbitMQ should be a viable solution for integrating disparate systems.
The poster child for scalable messaging systems, RabbitMQ has been used in countless large scale systems as the messaging backbone of any large cluster, and has proven itself time and again in many production settings.
Rabbit acts as our coordinator for all actions that happen during game time. All worker containers connect to rabbit in order to receive game events and emit their own events when applicable.
Used as central Message Broker; off-loading tasks to be executed asynchronous, used as communication tool between different microservices, used as tool to handle peaks in incoming data, etc.
RabbitMQ is the enterprise message bus for our platform, providing infrastructure for managing our ETL queues, real-time event notifications for applications, and audit logging.