MQTT Broker Server
Introduction of MQTT publish/subscribe model
MQTT is based on the Publish/Subscribe model for communication and data exchange, which is essentially different from the Request/Response model of HTTP.
Subscribers will subscribe to a Topic to the Broker. After a successful subscription, the broker forwards the message under the topic to all subscribers.
The topic uses ‘/’ as a separator to distinguish between different levels. Topics containing the wildcard ‘+’ or ‘#’ are also called as Topic Filters, and topics without wildcards are called Topic Names. E.g:
Introduction of MQTT Broker/Server
MQTT Broker definition and function
MQTT Broker, also known as the MQTT Message Server, can be a server or a cluster of servers running MQTT Message Server software. MQTT Broker is responsible for receiving network connections from the client and handling the client’s requests of Subscribe/Unsubscribe and Publish, as well as forwarding the messages published by the client to other subscribers.
MQTT Broker is widely used in the industries of power, new energy, smart city, smart home, smart meter reading, vehicle networking, finance and payment, operators and so on.
Common open source MQTT broker/server
- EMQ X — EMQ X is developed based on the Erlang/OTP platform and is the most popular MQTT broker in the open source community. In addition to the MQTT protocol, EMQ X also supports protocols such as MQTT-SN, CoAP, LwM2M, and STOMP. Currently, EMQ X has more than 5,000 corporate users and more than 20 partners of the world top 500 in the global market.
- Eclipse Mosquitto- Mosquitto is an early open source MQTT Broker that includes a C/C++ client library and command line clients of
mosquitto_subfor publishing and Subscribing. Mosquitto is lightweight and suitable for use on all devices from low-power single-board computers to servers.
- VerneMQ — VerneMQ is a high-performance, distributed MQTT message broker. It scales horizontally and vertically on commodity hardware to support a high number of concurrent publishers and consumers while maintaining low latency and fault tolerance. VerneMQ is a reliable message hub for your IoT platform or smart products.
- HiveMQ CE — HiveMQ CE is a Java-based open source MQTT broker that fully supports MQTT 3.x and MQTT 5. It is the foundation of the HiveMQ Enterprise Connectivity and Messaging Platform.
Main functions implemented by MQTT Broker
- Full MQTT V3.1/V3.1.1 and V5.0 protocol specification support;
- IoT protocol access support such as MQTT-SN, CoAP, lwM2M.
Support multi-server node clustering and support automatic discovery of nodes. Compared to a single server, a cluster can bring the following advantages through collaboration between multiple servers:
- High availability. Failures of a single or a small number of the server will not cause the stop of entire message service, and the remaining nodes that are working normally can continue to provide services;
- Load balancing. Through the load balancing mechanism, the cluster can distribute the load evenly across the nodes;
- Higher overall performance. Compared with single deployment, multi-node clusters can double the connection and message processing capabilities of the entire system;
- Scalability. Capacity expansion can be done by adding new nodes to the cluster without downtime.
- SSL, WSS encrypted connection, and single/two-way security authentication support ;
- Client ID, IP address, username and password, LDAP and browser cookie authentication support;
- Access Control (ACL) based on client ID, IP address, username;
- Limit of message rate and connection rate.
The main usage scenarios of data persistence include recording the client’s online and offline status, subscribed topic information, message content, and sending message receipts after the message arrives to various databases such as Redis, MySQL, PostgreSQL, MongoDB, and Cassandra.
- HTTP message publishing interface support, which makes it easier for upper-layer applications to send messages to devices through the REST API;
- MQTT Broker bridging, that supports message bridging between different MQTT Brokers or different clusters. Bridging makes it easy to bridge messages to cloud services, streaming services, or other MQTT message servers. Bridging can accomplish some functions that cannot be achieved by simply using a cluster, such as deploying across VPCs, supporting heterogeneous nodes, and increasing the service limit for a single application;
- Support for shared subscriptions. Shared subscription is a mechanism that allows the distribution of messages for a subscription group to be evenly distributed to members of a subscription group. In a shared subscription, clients that subscribe to the same topic receive messages under this topic in turn. The same message will not be sent to multiple subscribing clients, thus achieving load balancing between multiple subscribing clients;
- Rule engine support for configuring the processing and response rules of message streaming and device events. The rules describe three configurations of where the data comes from, how to filter and process the data, where the results go to. One of the available rules contains three elements: trigger event ( Trigger when satisfying certain conditions, process rules (filtering and processing data from context information), response actions (such as persistence to a database, republishing processed messages, forwarding messages to message queues, etc.).
Use of MQTT Broker
Broker address： broker.emqx.io
Broker port： 1883、8883（SSL）、8083（Websocket）、8084（WSS）
MQTT Broker connection
Open the address MQTT WebSocket Toolkit using the browser, click the New Connection button in the lower left corner, and fill in the link information in the box on the right. Fill out the required fields and click the Connect button to create a link and connect to the Broker.
After the connection is successful, click Write a message in the lower right corner to pop up the message publishing box, fill out Topic and Payload and click the send icon to publish the message.
- Subscribe to regular topics
- In the Subscriptions module, subscribe to the hello topic. At this point, if you send a message to the hello topic, the message will be received in the message list (the message received on the left).
- Subscribe to wildcard topics
- Subscribe to the wildcard topic testtopic/# and send a message to the testtopic/1 topic, which will be received in the message list.