MQTT vs. Kafka: An IoT Advocate's Perspective

Re:MQTT vs. Kafka: An IoT Advocate's Perspective by ClumsyPilot on Tuesday March 14, 2023 @07:10PM (#35160687)

You are absolutely right, but not every project needs reliable messaging.

Many projects can be just fine with ephemeral messaging, they might already have some kind of managed scalable database and failures can often be handled on the client side.

Often we insert messaging into an HTTP system, or replace an HTTP system. In those cases, the client is waiting for an acknowledgement from the system that sits on the other side of the queue.

What happens in HTTP is you send a request to an HTTP server, but it combusts before you get a responce? Connection breaks or you get "request timed out" and user can click the button again. Or you can retry in the client code.

For many joke apps it is not always worthwhile to double complexity to move from a 98% system to a 100% system.

[ Parent | on HN ]

Re:MQTT vs. Kafka: An IoT Advocate's Perspective by rad_gruchalski on Tuesday March 14, 2023 @07:50PM (#35161351)

Yes, I agree wholeheartedly. If you don’t need reliable replication and can tolerate data loss, whatever rocks your boat :)

Personally, I do not find Kafka difficult to operate. ZooKeeper is basically a boring black box and there’s also kraft (the famous KIP-500).

[ Parent | on HN ]

Re:MQTT vs. Kafka: An IoT Advocate's Perspective by petre on Wednesday March 15, 2023 @01:33AM (#35164314)

> You are absolutely right, but not every project needs reliable messaging.

Until a manager comes on and decides it does and you have to redesign everything related to the message queue.

[ Parent | on HN ]