ActiveMQ vs RabbitMQ: What are the differences?
Developers describe ActiveMQ as "A message broker written in Java together with a full JMS client". Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License. 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.
ActiveMQ and RabbitMQ can be categorized as "Message Queue" tools.
"Open source" is the primary reason why developers consider ActiveMQ over the competitors, whereas "It's fast and it works with good metrics/monitoring" was stated as the key factor in picking RabbitMQ.
ActiveMQ and RabbitMQ are both open source tools. RabbitMQ with 5.88K GitHub stars and 1.73K forks on GitHub appears to be more popular than ActiveMQ with 1.49K GitHub stars and 1.04K GitHub forks.
According to the StackShare community, RabbitMQ has a broader approval, being mentioned in 921 company stacks & 532 developers stacks; compared to ActiveMQ, which is listed in 33 company stacks and 17 developer stacks.
What is ActiveMQ?
What is RabbitMQ?
Want advice about which of these to choose?Ask the StackShare community!
What are the cons of using ActiveMQ?
What tools integrate with ActiveMQ?
What tools integrate with RabbitMQ?
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.
RabbitMQ is an all purpose queuing service for our stack. We use it for user facing jobs as well as keeping track of behind the scenes jobs.