VolantMQ is a high performance MQTT broker that aims to be fully compliant with MQTT specs
Features, Limitations, and Future
- MQTT v3.1 - V3.1.1
- MQTT V5.0
- WebSockets transport
- SSL for both plain tcp and WebSockets transports
- Independent auth providers for each transport
- Persistence providers
- In memory
Project has been tested with the following client libraries
- Paho MQTT Conformance/Interoperability Testing Suite (in Python)
- Pass with all of the test cases
- Paho C Client library (in C)
- Pass with all of the test cases
How to use
Best option is to run prebuilt docker image
docker run --rm -p 1883:1883 -p 8080:8080 -v $(pwd)/examples/config.yaml:/etc/volantmq/config.yaml --env VOLANTMQ_CONFIG=/etc/volantmq/config.yaml volantmq/volantmq
- In example above port 1883 is mqtt listener with default user/password testuser/testpassword
- Port 8080 exposes healthcheck endpoints as well as pprof at http://localhost:8080/debug/pprof
Appreciate JetBrains for granted license
Package volantmq is a high performance MQTT broker and client library that aims to be fully compliant with MQTT 3.1 and 3.1.1 specs.
The primary package that's of interest is package service. It provides the MQTT Server and Client services in a library form.
MQTT is a Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium. The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include: - Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications. - A messaging transport that is agnostic to the content of the payload. - Three qualities of service for message delivery: - "At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after. - "At least once", where messages are assured to arrive but duplicates can occur. - "Exactly once", where message are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied. - A small transport overhead and protocol exchanges minimized to reduce network traffic. - A mechanism to notify interested parties when an abnormal disconnection occurs.
Current performance benchmark of VolantMQ, running all publishers, subscribers and broker on a single 4-core (2.8Ghz i7) MacBook Pro, is able to achieve:
- over 400,000 MPS in a 1:1 single publisher and single producer configuration
- over 450,000 MPS in a 20:1 fan-in configuration
- over 750,000 MPS in a 1:20 fan-out configuration
- over 700,000 MPS in a full mesh configuration with 20 clients
In addition, VolantMQ has been tested with the following client libraries and it _seems_ to work:
- libmosquitto 1.3.5 (C)
- Tested with the bundled test programs msgsps_pub and msgsps_sub
- Paho MQTT Conformance/Interoperability Testing Suite (Python)
- Tested with all 10 test cases.
- Paho Go Client Library (Go)
- Tested with one of the tests in the library, in fact, that tests is now part of the tests for VolantMQ
- Paho C Client library (C)
- Tested with most of the test cases and failed the same ones as the conformance test because the features are not yet implemented.
- Actually I think there's a bug in the test suite as it calls the PUBLISH handler function for non-PUBLISH messages.