NSQ vs RabbitMQ: What are the differences?
What is NSQ? A realtime distributed messaging platform. NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.
What is 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.
NSQ and RabbitMQ can be primarily classified as "Message Queue" tools.
Some of the features offered by NSQ are:
- support distributed topologies with no SPOF
- horizontally scalable (no brokers, seamlessly add more nodes to the cluster)
- low-latency push based message delivery (performance)
On the other hand, RabbitMQ provides the following key features:
- Robust messaging for applications
- Easy to use
- Runs on all major operating systems
"It's in golang" is the top reason why over 23 developers like NSQ, while over 203 developers mention "It's fast and it works with good metrics/monitoring" as the leading cause for choosing RabbitMQ.
NSQ and RabbitMQ are both open source tools. It seems that NSQ with 15.6K GitHub stars and 2.03K forks on GitHub has more adoption than RabbitMQ with 5.94K GitHub stars and 1.78K GitHub forks.
reddit, 9GAG, and Rainist are some of the popular companies that use RabbitMQ, whereas NSQ is used by Stripe, Docker, and Segment. RabbitMQ has a broader approval, being mentioned in 940 company stacks & 548 developers stacks; compared to NSQ, which is listed in 21 company stacks and 8 developer stacks.
What is NSQ?
What is RabbitMQ?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with NSQ?
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.
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.