48 engineers on Hacker News describe using RabbitMQ first-hand: 11 endorse it, 10 regret it, 5 are mixed.
“We had never ending problems after that, many of them were misunderstandings, some where just wrong-fit.”
regret · production · throwitaway222 · 2026-08-20 · source ↗ · wrong label?“At some point we were able to stabilize it (a bunch of magic tricks and patches) and froze every related piece; it worked well under pressure (thanks, RabbitMQ).”
endorse · production · leobuskin · 2025-12-10 · source ↗ · wrong label?“We found bull had a much lower throughput, after a lot of tuning compared even to rabbit out of the box.”
endorse · production · abe94 · 2024-09-18 · source ↗ · wrong label?“I have used the usual tools like Redis and RMQ... I wouldn't mind at all to get rid of another system (not just one server but the cluster of RMQ/Redis you need for HA)”
regret · production · lazyant · 2023-11-20 · source ↗ · wrong label?“Three years ago, I worked on a project that used the software for a Celery queue. Messages would occasionally go missing”
regret · production · mianos · 2023-09-25 · source ↗ · wrong label?“The business logic message passing goes through Rabbit because we wanted out of order processing, priority routing, retry queues”
endorse · production · Spivak · 2023-09-21 · source ↗ · wrong label?“Our problem was that when a consumer hung on a poison pilled message, the prefetched messages would not be released.”
regret · production · phamilton · 2023-04-11 · source ↗ · wrong label?“the only time the rabbitmq cluster had outages was when it got confused and thought (incorrectly) there was a network partition”
regret · production · shoo · 2021-12-18 · source ↗ · wrong label?“While RabbitMQ is not a “never again” for me, I agree that making it work reliably does involve a few knobs and architectural tricks.”
mixed · production · turtlequeue · 2021-05-18 · source ↗ · wrong label?“RabbitMQ went on my "never again" list of things after dealing with it for years as part of OpenStack”
regret · production · jpgvm · 2021-05-17 · source ↗ · wrong label?“I love RabbitMQ but deploying/managing a cluster can be tricky. We had problems with network partitioning and since we didn't really need a cluster for performance reasons”
mixed · production · jugg1es · 2020-05-21 · source ↗ · wrong label?“RabbitMQ gave us such a performance increase that we killed our database. We ended up having to rate limit RabbitMQ!”
mixed · production · larrik · 2020-05-21 · source ↗ · wrong label?“"Managing" RabbitMQ is not rocket science. But these days, I don't deal with managing infrastructure.”
mixed · production · scarface74 · 2018-12-28 · source ↗ · wrong label?“the closest I ever came to using a functionally developed product was RabbitMQ... That one was such a pain to use and operate”
regret · production · endymi0n · 2018-12-27 · source ↗ · wrong label?“Once it's setup and running, it works well enough.”
mixed · production · vorpalhex · 2018-05-14 · source ↗ · wrong label?“it's saved a massive amount of time and effort and has made debugging and tracing issues so much easier”
endorse · production · scaryclam · 2017-11-13 · source ↗ · wrong label?“Right now we use Rabbit, which is terrible for some reasons I won't get into”
regret · production · djsumdog · 2016-12-13 · source ↗ · wrong label?“With RabbitMQ I've seen the queue grow to about 120K without so much as a single hiccup.”
endorse · production · asadjb · 2016-11-13 · source ↗ · wrong label?“In our case, it's definitely easier/cheaper/better to install RabbitMQ.”
endorse · production · cookiecaper · 2016-04-06 · source ↗ · wrong label?“my negative experiences with RabbitMQ at the time (very unstable, and not actually that performant) made me leery of using it in production code”
regret · production · cmrdporcupine · 2015-06-01 · source ↗ · wrong label?“We run a RabbitMQ cluster behind a load balancer, and it works great”
endorse · production · brassybadger · 2014-03-30 · source ↗ · wrong label?“we also use a number of other great technologies like CouchDB (specifically BigCouch), RabbitMQ, OpenSIPS”
endorse · production · josh2600 · 2012-07-10 · source ↗ · wrong label?“We switched from ActiveMQ (with JMS) to RabbitMQ (with AMQP) on our enterprise grade application, and we are extremely happy with it.”
endorse · production · sgt · 2010-11-13 · source ↗ · wrong label?“I've been using another Erlang product recently, RabbitMQ, and the way you can just throw thousands upon thousands of messages on it”
endorse · personal · sgt · 2010-10-11 · source ↗ · wrong label?“we've had serious issues with rabbitmq reliability under load (and debugging the problems thereafter!)”
regret · production · moe · 2010-05-16 · source ↗ · wrong label?“it's still pretty trivial to set up and get running”
endorse · production · wooster · 2010-03-31 · source ↗ · wrong label?“We have periodic problems with celery: workers losing connection with RabbitMQ, Celery itself getting stuck”
neutral · production · pmontra · 2025-11-29 · source ↗ · wrong label?“communicating with the usual suspects; Postgres, RabbitMQ, etc.”
neutral · production · adampwells · 2023-12-15 · source ↗ · wrong label?“we rely on Spring and RabbitMQ heavily.”
neutral · production · jmaker · 2023-11-23 · source ↗ · wrong label?“Celery with RabbitMQ/Redis for task processing.”
neutral · production · clepto · 2021-12-07 · source ↗ · wrong label?“a huge issue with a change in how LShift was hosting RabbitMQ, and I was able to move my company's cluster over to CloudAMQP instead.”
neutral · production · rpdillon · 2021-08-09 · source ↗ · wrong label?“inertia/time constraints have made it hard to consider moving away from Rabbit.”
neutral · production · suresk · 2021-05-17 · source ↗ · wrong label?“two or three node clusters running in non-prod environments on virtual machines running Windows. In Prod, three node clusters on Windows virtual machines.”
neutral · production · hnrodey · 2020-05-21 · source ↗ · wrong label?“We use RabbitMQ hosted on Azure via CloudAMQP.”
neutral · production · LandR · 2019-08-21 · source ↗ · wrong label?“the above list covers us off pretty well for our architecture that uses RabbitMq for messaging”
neutral · production · junto · 2018-12-19 · source ↗ · wrong label?“We run our RabbitMQ cluster with pause_minority as the partition handling strategy.”
neutral · production · xerxes901 · 2017-08-27 · source ↗ · wrong label?“rawrabbit (simple rabbitmq library)”
neutral · production · jayrulez · 2017-01-31 · source ↗ · wrong label?“We run an average of 14k logs/sec through a two-node RMQ cluster”
neutral · production · packetized · 2016-09-17 · source ↗ · wrong label?“a fully async eventing pipe line for workflows built on RabbitMQ makes for an infinitely expandable fraud detection system.”
neutral · production · virmundi · 2016-09-12 · source ↗ · wrong label?“In our environment we run tasks on RabbitMQ/Celery.”
neutral · production · LukaAl · 2015-05-20 · source ↗ · wrong label?“a new side-project... with RabbitMQ handling the messaging, Bunny to handle message processing and Sinatra/Faraday”
neutral · personal · kfullert · 2014-11-26 · source ↗ · wrong label?“I forced myself to use Haskell for everything: build scripts, RabbitMQ consumer, web app.”
neutral · personal · shadytrees · 2014-06-24 · source ↗ · wrong label?“Erlang, haproxy, rabbitmq, redis, postgres, cassandra, chef”
neutral · production · metabrew · 2013-11-29 · source ↗ · wrong label?“All the irc messages end up in cassandra, via rabbitmq.”
neutral · production · metabrew · 2013-11-29 · source ↗ · wrong label?“For Fashiolista we currently use celery with rabbitmq and have different queues and worker clusters”
neutral · production · tschellenbach · 2013-10-15 · source ↗ · wrong label?“I am tying everything together with RabbitMQ, so scaling is doable.”
neutral · production · philippeback · 2013-10-13 · source ↗ · wrong label?“I've only been using 0MQ as a library and AMQP in the form of RabbitMQ”
neutral · personal · wink · 2011-11-11 · source ↗ · wrong label?“It had MySQL with a prod snapshot, RabbitMQ, a Django web app and a bunch of twisted services.”
neutral · personal · 1 yr · AngryParsley · 2011-09-19 · source ↗ · wrong label?