4 ms·
I feel like RabbitMQ is sort of the "swiss army knife" of message queues, and I mean that in the nicest way possible. People will compare it to Kafka, claiming
by tombert 6y ago
I feel like RabbitMQ is sort of the "swiss army knife" of message queues, and I mean that in the nicest way possible.
People will compare it to Kafka, claiming that its pubsub is faster than Rabbit's, but that's sort of missing the point: Rabbit thrives because it's easy to set up, will work well for 99% of cases, and handles nearly every kind of distributed problem you're likely to come across.
I recently did a project with Rabbit on my home server, and while the project had some issues, the issues were never Rabbit.
- fernandotakai 6y agoit's also super duper stable even on default configs. it's one of my favorite softwares ever.
- wenc 6y agoRabbit doesn't have Kafka's ability to massively distribute and scale (it does have a distributed story but from what I hear few explore it). But Rabbit also supports more complex use cases than Kafka because its messaging protocol (AMQP) is more intelligent. Unless you're a "web-scale"/s company, Rabbit's scale even on one node is likely enough. I've been using Rabbit in production for RPC and pub/sub for the past 5 years (single instance running on a non-dedicated VM, medium traffic) and its been pretty easy to setup and has been pretty reliable in practice. I've always been concerned about losing messages, and I did have to learn to turn on persistence and durability for messages to survive server interruptions, but it was easy enough. Message acknowledgements are also a nice feature, and Rabbit is able to achieve at-least-once messaging semantics.
- tombert 6y agoYeah, I don't dispute that for certain usecases, Kafka is definitely the better choice, use the right tool for the right job. That said, for most small to medium-large tasks, Rabbit will handle things without much trouble, making it a good fit for most common usecases.