In MQTT, both the client and the server can send a DISCONNECT packet to the other party before disconnecting the network connection, indicating the reason for the connection closure.

MQTT has a type of packet used to simulate heartbeats between the client and server to maintain the connection. They are PINGREQ and PINGRESP packets, which we often call heartbeat packets.

In MQTT, the SUBSCRIBE packet is used to initiate a subscription request, while the SUBACK packet is used to return the subscription result. The UNSUBSCRIBE and UNSUBACK packets are used when unsubscribing.

This blog will introduces the PUBLISH packet used to deliver application messages in MQTT, and its response packets.

RabbitMQ is an open-source message-broker software that transmits data between applications and services. Kafka is an open-source distributed message streaming platform.

MQTT connection requires CONNECT and CONNACK packets. CONNECT initiates the request and server responds with CONNACK indicating connection result.

This blog will introduce each new feature introduced in 5.0 in turn, and use the MQTTX CLI tool to demonstrate how we can use these features in EMQX.

This blog provides a simple Unity3d project for using M2MQTT with Unity. The project includes an example scene with a user interface for managing the connection to the broker and testing messaging.

Eclipse Mosquitto is an open-source message broker that uses the MQTT (Message Queuing Telemetry Transport) protocol.

This article will introduce the basic principles of Token-Based Authentication based on JWT, and how to build your own JWKS Endpoint.

Understand what authorization is and common methods in MQTT. Learn how to use ACLs to control access to MQTT messaging.

MQTT (Message Queuing Telemetry Transport), is a lightweight publish/subscribe messaging protocol. AMQP (Advanced Message Queuing Protocol), is a protocol for distributed systems that supports a range of messaging patterns