RabbitMQ
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
3recommend
1warn against
Jan 12, 2026first mention
Oct 26, 2026latest mention
Why people recommend it
“I don't know the internals of Kafka, RabbitMQ, or PostgreSQL. I just know how to use them. And yet they work fine.”
on-site programmeron “The Tower Keeps Rising”
“I love rabbitmq. It's an amazing technology”
Show 1 more
“RabbitMQ is also very good”
no production experience with iton “I Replaced Kafka, Redis, and RabbitMQ with One Tool …”
Caveats and dissent
“We had never ending problems after that”
switched from PostgreSQLon “PostgreSQL for Everything”
Often compared with
Who recommends it in their own words
Threads where it came up
- Why is it so expensive to send an email? 1 mention
- PostgreSQL for Everything 1 mention
- The Tower Keeps Rising 1 mention
- You probably don't need another database 1 mention
- I Replaced Kafka, Redis, and RabbitMQ with One Tool – A Deep Dive into NATS 1 mention
- Message Queues: A Simple Guide with Analogies 1 mention
Data: rabbitmq.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 6
“A long time ago I used RabbitMQ at the heart of a service built on top of an existing relatively modest fleet of SMTP servers.”
“We had never ending problems after that”
“I don't know the internals of Kafka, RabbitMQ, or PostgreSQL. I just know how to use them. And yet they work fine.”
“I love rabbitmq. It's an amazing technology”
“RabbitMQ is also very good”
“having just migrated a set of message queues and streams from AWS(AvtiveMQ) to RabbitMQ”