4 ms·
This article appears to be comparing MQTT and Kafka + Schema Registry. Using Schema Registry is not required to use Kafka, so OP overcomplicated their own set u
by Jemaclus 4y ago
This article appears to be comparing MQTT and Kafka + Schema Registry. Using Schema Registry is not required to use Kafka, so OP overcomplicated their own set up for this comparison. There's no argument that Schema Registry is valuable, but it's not something that MQTT seems to provide out of the box, so the comparison seems flawed.
I'd be interested in a comparison that is actually apples-to-apples instead of introducing complexity with Schema Registry.
- rad_gruchalski 4y agoComparing mqtt to kafka is already apples vs oranges. Adding the schema registry to this is like throwing a pitaya into the mix. Edit: after reading the article a couple of times it’s clear this isn’t a comparison. “Vs” in the title is the problem. The first impression would have been better if the title was something like ”Kafka and MQTT“. To be honest, as kafka and mqtt often reside next to each other, they complement each other. A better use case would have been an app combining both: show when should mqtt hand over to kafka.
- deleted 4y ago[deleted]
- stingraycharles 4y agoCan confirm, I work with several workloads where MQTT is used to aggregate IoT data close to the source, which is then pushed into the cloud which uses Kafka.
- ryanjshaw 4y agoThe author is also incorrect about message keys - these are optional and you would only use them for strict ordering when using > 1 partition, or log compaction where "latest is greatest" is good enough.