RabbitMQ

Raised as a usability problem by 14 people on Hacker News over 13 years (2014–2026), in 11 threads.

People raised many different problems with RabbitMQ, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 13 complaints

Took a full day of jumping through hoops to get it working2026-08-19
Configuration is full of pitfalls, so clustered setups can fail or double-consume messages2023-09-25
Documentation and search lead developers down the hard path instead of the easy one2023-04-12
RabbitMQ libraries and tooling are unintuitive and confusing without a higher-level layer2023-04-12
Every node must run the exact same version, so zero-downtime upgrades are impossible2022-07-14
Cannot bind cluster port 25672 to localhost, exposing it to the internet2022-07-14
Erlang-style config files are basically unreadable, and invalid-config error messages are confusing2021-06-12
Easy to misconfigure queues and exchanges, especially retry plus DLQ setups2021-05-17
Simple fan-out setup needs intricate code; declaring the same queue twice breaks2020-05-22
Painful to work with and almost impossible to set up locally2020-05-22
Must match Erlang versions; wrong versions give hard-to-understand errors2019-09-30
Can't peek into queue contents or count messages without consuming them2017-09-21
Message queue documentation is so complex that understanding the broker's model takes long study2014-03-30