Clustering MQTT - New Blog Post Series
MQTT servers are critical pieces of a messaging infrastructure and are part of the business critical application backbone that must not fail. The scalable Publish / Subscribe architecture of MQTT depends on a MQTT broker as central distributor of messages. To circumvent such a single point of failure in messaging systems (if a broker is offline, clients can’t communicate!), MQTT broker clusters are required.
This blog post series discusses why a MQTT broker cluster is needed for professional MQTT deployments. You’ll learn that network partitions must be supported by brokers in cloud environments and that a MQTT broker cluster needs to be resilient and available all the time since a broker cluster is one logical MQTT broker from a MQTT client’s perspective, which also means that a broker must never lose any MQTT sessions, even when topology changes occur.
Read this weeks blog post to learn about:
- What a MQTT broker cluster is
- Why a broker cluster must not trade partition tolerance
- Advantages of creating a MQTT broker cluster
- How HiveMQ helps creating resilient, highly available and linearly scalable clusters