MQTT vs RabbitMQ: What are the differences?
MQTT: A machine-to-machine Internet of Things connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium; 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.
MQTT and RabbitMQ can be primarily classified as "Message Queue" tools.
RabbitMQ is an open source tool with 5.95K GitHub stars and 1.78K GitHub forks. Here's a link to RabbitMQ's open source repository on GitHub.
reddit, 9GAG, and Rainist are some of the popular companies that use RabbitMQ, whereas MQTT is used by Pubu, Jaumo, and Danale Inc. RabbitMQ has a broader approval, being mentioned in 941 company stacks & 551 developers stacks; compared to MQTT, which is listed in 12 company stacks and 6 developer stacks.
What is MQTT?
What is RabbitMQ?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose MQTT?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using MQTT?
Sign up to get full access to all the companiesMake informed product decisions
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.