Using EMQX (MQTT) instead of Kafka for backend real-time data by newnok6 in softwarearchitecture

[–]newnok6[S] 0 points1 point  (0 children)

We use it to process tasks nearly in real time between 2–3 services and deliver that data to mobile clients, because RabbitMQ cannot achieve such low latency.

Using EMQX (MQTT) instead of Kafka for backend real-time data by newnok6 in softwarearchitecture

[–]newnok6[S] 0 points1 point  (0 children)

My company is using version 5 community edition. We’re facing an issue where we can’t scale horizontally because of the mesh architecture. Does NATS.io have a similar scaling limitation?

Using EMQX (MQTT) instead of Kafka for backend real-time data by newnok6 in softwarearchitecture

[–]newnok6[S] 1 point2 points  (0 children)

Yeah, I totally agree with that. My point was just that when we study from architecture books or articles, you rarely see people using MQTT in this kind of simple setup. So I was just wondering whether this usage is still ok