Professional Documents
Culture Documents
Clustering HiveMQ
Clustering HiveMQ
5/2016
About this document
MQTT is based on a publish/subscribe architecture that decouples MQTT clients
and uses a central MQTT broker for distributing messages in a very performant and
efficient manner. Traditionally, MQTT brokers are deployed as a single instance. This
makes a broker deployment hard to scale and the single deployment is a Single
Point of Failure, which means the whole MQTT communication is offline when the
single broker fails.
This document discusses how you can eliminate these problems by creating a MQTT
broker cluster that is scalable in a horizontal fashion (which means you can add any
number of MQTT brokers at runtime) and eliminates the single point of failure by
clustering multiple broker nodes to one logical MQTT broker. You will learn how you
achieve true high availability and linear scalability with HiveMQ.
Table of Contents
1. Introduction .. 2
2. The Only MQTT Broker that scales horizontally 2
3. The Distributed Cluster explained .. 2
4. Availability - Paramount for the IoT . 3
5. Best in Class Performance and Scalability . 4
6. Zero Downtime Upgrades . 4
7. Discovery Mechanisms ...... 4
8. Support for all Major OS and Cloud Providers ........ 5
9. A Plugin System designed for MQTT Broker Clusters 5
10. Conclusion .... 6
Conclusion
Support for all Major OS
Due to HiveMQs sophisticated cluster
and Cloud Providers
design that is tailored specifically for
MQTT, HiveMQ is able to form highly-
When it comes to HiveMQ deploy-
available, elastically and horizontally
ments, public cloud providers like
scalable MQTT Broker clusters that
AWS, Microsoft Azure and Google
avoid a Single Point of Failure. The
Cloud Platform are first-class citizens
cluster is linearly scalable and nodes
as well as hybrid or private clouds.
can be added and removed at run-
HiveMQ runs on any operating system
time without any service interruption.
like Linux (e.g. RHEL, CentOS, Ubun-
tu, Debian) or Microsoft Windows
HiveMQ is designed to handle net-
Server.
work splits and the system is always
Its easy to scale out your cluster de- available, even if some parts of the in-
frastructure become unavailable. Ad-
ployments with Docker and tools like
vanced self-healing mechanisms pro-
Kubernetes or Mesos (with Marathon).
tect from fatal disasters.