| MQTT and Kafka are different things. MQTT is not necessarily better or worse than Kafka, vice versa. But, sadly, people are often caught in their own loops, when there are or can be created better options. I have created a new, free, single binary data-service platform for IoT, JoinBase: https://joinbase.io/ This single binary data-service platform has proved: 1. Kafka is not more suitable for industry or higher performance than MQTT, even from the protocol level With carefully crafting, JoinBase has saturated one PCIE 3.0 NVME sustained write bandwidth (25 million msg/s) in single modern node. This is, in fact, can not been done by the Java-based Kafka. We have provided FREE full functionality community for testing: https://joinbase.io/products/ 2. Use MQTT and Kafka together is unnecessary.
This only makes your pipeline more complex, expensive, but much unstable and slower. JoinBase can do arbitrary message preprocessing and auto-view(WIP). Streaming does not have to be owned through a separate monster. 3. High performance or ease of use, has nothing to do with the size of the software if the product can be properly engineered. 5MB Single binary JoinBase is enough to beat many monsters in the IoT/AIoT data pipleine:
+ sustained batch MQTT message write throughput: ~10x faster than Kafka and ~5x faster than that of one popular broker
+ basic SQL analytics: 3-4x faster than ClickHouse
+ HTTP interface concurrent queries: ~100x higher than ClickHouse
+ ...
More could be seen in our 2022 summary blog: https://joinbase.io/blog/joinbase-2023/ There are historical reasons for all of these, of course. But it could be great that we break out of own mindset loops. |