News for hackers. Stuff that matters.

A comment on RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1). Parent comment

Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by KaiserPro on Tuesday September 19, 2023 @05:20PM (#37576905)
Rabbit is an arse to scale past one broker. It was possible, but a pain, that might have changed.

Kafka is just a pain full stop.

[ Parent | on HN ]
Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by nhumrich on Tuesday September 19, 2023 @05:36PM (#37577114)
The official rabbitmq controller for kubernetes is a breeze. Scales wonderfully without almost any effort.
[ Parent | on HN ]
Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by icedchai on Tuesday September 19, 2023 @06:03PM (#37577529)
At a previous company, about 10 years ago, we had roughly 10 RabbitMQ instances (brokers), all isolated. The system was essentially partitioned by queue server. We had a directory-ish service that would associate clients with their assigned node. It worked well, except if a client got too large we might have to move them to another queue.
[ Parent | on HN ]