kafka sum mqtt

Although both evolved from the traditional Pub/Sub message system, the evolution direction is different. The following are a few more prominent points: Kafka is for data integration scenarios, which is different from the previous Pub/Sub message bus. , through the distributed architecture, it provides features such as massive message processing, high fault-tolerant storage of massive data streams, and guaranteeing the order of data streams. See Kafka on the Cloud - Data Union. MQTT is optimized for IoT scenarios. It not only provides multiple QoS options (exact once, at least once, at most once), but also features hierarchical topics, wills, and more. You can refer to MQTT Introduction - Data Union. To put it bluntly, they are all descendants of the traditional messaging system (father), and are just the product of combining with different scenarios (mom). However, the two can be used in combination. For example, you can use MQTT to accept the data uploaded by IoT devices, then connect to Kafka, and finally distribute to HDFS for archiving, data warehouse for OLAP analysis, and Elasticsearch for full-text retrieval. This architecture is very suitable for large-scale IoT projects. Data is also very scalable.

Author: Zhang Qi
Link : https://www.zhihu.com/question/30343125/answer/81954454
Source: Zhihu The
copyright belongs to the author. For commercial reprints, please contact the author for authorization, and for non-commercial reprints, please indicate the source.