Introduction

Introduction

HiveMQ is a MQTT broker tailored specifically for enterprises, which find themselves in the emerging age of Machine-to-Machine communication (M2M) and the Internet of Things.
It was built from the ground up with maximum scalability and enterprise-ready security concepts in mind. HiveMQ implements the MQTT protocol, the de-facto M2M messaging standard, and through its 100% compliance to the specification, it is leading when it comes to professional adoption of all possibilities of the Internet of Things for companies.
As members of the OASIS committee, the HiveMQ team was directly involved in the creation and release of MQTT 5.0, the newest version of the lightweight protocol.

Tip

New to MQTT? If you are new to MQTT and want to learn about the specific protocol features and concepts, we recommend to read our MQTT Essentials series. In this series you can learn about: An introduction to MQTT Publish & Subscribe Basics Client, Broker and Connection Establishment Publish, Subscribe & Unsubscribe Topics & Best Practices Quality of Service Levels Persistent Session and Queuing Messages Retained Messages Last Will and Testament Keep Alive & Client Take-Over MQTT over WebSockets

HiveMQ MQTT compliance

HiveMQ Community Edition is 100% MQTT compliant and implements all MQTT features.

Supported MQTT versions

The following MQTT versions are fully supported:

• MQTT 3.1

• MQTT 3.1.1

• MQTT 5.0

Supported MQTT features

All MQTT features are 100% supported for single node and {cluster}[clustered deployments], including:

• Retained Messages

• QoS 0

• QoS 1

• QoS 2

• Clean & Persistent Sessions

• Queued Messages

• Last Will and Testament (LWT)

• Dynamic Topics

• Wildcard Subscriptions

• Username / Password Fields

• MQTT Client Takeovers

• MQTT Ordered Topic guarantees for QoS 1 and 2

• MQTT Client Load Balancing with Shared Subscriptions

Additional features

HiveMQ adds many additional features on top of its MQTT core, including:

• WebSockets

Note	Third party MQTT libraries All additional features are compatible with most MQTT client libraries.

Acknowledging QoS 1 messages

HiveMQ acknowledges an incoming QoS 1 message directly after the message arrived at the broker. Onward delivery to subscribing clients locally and in the cluster takes place immediately after message receipt as defined in the MQTT Specification.