Kestrel vs RabbitMQ: What are the differences?
Kestrel: Simple, distributed message queue system. Kestrel is based on Blaine Cook's "starling" simple, distributed message queue, with added features and bulletproofing, as well as the scalability offered by actors and the JVM; RabbitMQ: 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.
Kestrel and RabbitMQ can be primarily classified as "Message Queue" tools.
Some of the features offered by Kestrel are:
- Written by Robey Pointer
- Starling clone written in Scala (a port of Starling from Ruby to Scala)
- Queues are stored in memory, but logged on disk
On the other hand, RabbitMQ provides the following key features:
- Robust messaging for applications
- Easy to use
- Runs on all major operating systems
Kestrel and RabbitMQ are both open source tools. RabbitMQ with 5.94K GitHub stars and 1.78K forks on GitHub appears to be more popular than Kestrel with 2.8K GitHub stars and 326 GitHub forks.
What is Kestrel?
What is RabbitMQ?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose Kestrel?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Kestrel?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Kestrel?
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.