Hacker News new | ask | show | jobs
by alternative_a 920 days ago
Neither assumption holds. RabbitMQ is built on top of OTP. MQTT is a protocol which means client lang stack makes no difference.

To be clear, I am not asking why not Rabbit instead of Kafka. No. Why not just RabbitMQ with MQTT plugin instead of this broker.

1 comments

RabbitMQ with the MQTT plugin is actually a good choice for many scenarios, especially when you need a messaging system that supports the MQTT protocol alongside other messaging protocols like AMQP. However, as they themselves say, There are other good MQTT brokers out there, and some will be able to handle even more MQTT client connections than RabbitMQ because other brokers are specialised in MQTT only. TBMQ - is exactly such a MQTT broker that is designed to be scalable, fault-tolerant, and efficient. The recent performance tests showed the TBMQ quality. Additionally, TBMQ can be easily launched as a single server, two servers, three servers, and so on. Compared to RabbitMQ - https://www.rabbitmq.com/mqtt.html#requirements
Thanks (and good luck with the project!)
thank you, my friend :)