A quick introduction to MQTT message broking, the challenges of clustering, and then load balancing.
Join the DZone community and get the full member experience. This post gives a quick introduction to MQTT message broking, the challenges of clustering, and then load balancing. Maybe you are not that familiar with MQTT protocol, you probably know HTTP protocol very well. Like HTTP, MQTT works at the same network (transport) layer TCP/TLS (well, it can actually work on top of HTTP, but that’s a topic for another day). According to https://mqtt.org: MQTT is an OASIS standard messaging protocol for the Internet of Things (IoT). It is designed as an extremely lightweight publish/subscribe messaging transport that is ideal for connecting remote devices with a small code footprint and minimal network bandwidth. MQTT today is used in a wide variety of industries, such as automotive, manufacturing, telecommunications, oil and gas, etc. MQTT clients are also similar to HTTP clients: they establish TCP connections to a server and send and receive data. The difference is that HTTP uses a request/response model, while MQTT uses a publish/subscribe model. A real-life example: a temperature sensor in the living room periodically publishes its readings to an MQTT broker.
