MQTT messages are small and easy to encode and decode, while XMPP is based on heavy XML, and the messages are large and cumbersome to interact with.It will completely replace the PC-era XMPP protocol in the fields of Mobile Internet and IoT messaging. MQTT protocol is simple and lightweight in design and flexible in routing. MQTT can recover connections from abnormal disconnections, which HTTP cannot achieve.MQTT is stateful, but HTTP is stateless.MQTT can push messages in real-time, but HTTP needs polling for data updates.MQTT is based on a publish-subscribe model and HTTP is based on request-response, so MQTT supports duplex communication.Both MQTT and HTTP can use TCP connections and achieve stable and reliable network connections. With a minimum message size of 2 bytes, MQTT takes up less network overhead than HTTP.Comparison Between MQTT and Other Protocols The name MQ TT was chosen in accordance with industry practice because Nipper is a remote sensing and data acquisition and monitoring professional. Its purpose was to allow sensors to communicate with IBM's MQ Integrator via VSAT, which has limited bandwidth. It is a real-time data transmission protocol that he developed while working on a crude oil pipeline SCADA system for Conoco Phillips in the early 1990s. Continuous session awareness (always know whether the device is online)Īccording to Arlen Nipper on IBM Podcast, MQTT was originally named MQ TT.Data irrelevant (Payload data format does not matter).Lightweight and bandwidth-saving (because bandwidth was expensive back then).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |