NanoMQ

NanoMQ MQTT Broker (NanoMQ) is a lightweight and blazing-fast MQTT Broker for the IoT Edge platform.

NanoMQ bases on NNG's asynchronous I/O threading model, with an extension of MQTT support in the protocol layer and reworked transport layer, plus an enhanced asynchronous IO mechanism maximizing the overall capacity.

NanoMQ fully supports MQTT V3.1.1 and MQTT V5.0.

For more information, please visit NanoMQ homepage.

Features

Cost-effective on an embedded platform;
Fully base on native POSIX. High Compatibility;
Pure C implementation. High portability;
Fully asynchronous I/O and multi-threading;
Good support for SMP;
Low latency & High handling capacity;

Quick Start

NanoMQ broker usage

nanomq start 
nanomq stop
nanomq restart

MQTT Example:

nanomq start

NanoMQ MQTT client usage

# Publish
nanomq_cli pub --url <url> -t <topic> -m <message> [--help]

# Subscribe 
nanomq_cli sub --url <url> -t <topic> [--help]

# Connect
nanomq_cli conn --url <url> [--help]

NanoMQ MQTT bench usage

nanomq_cli bench { pub | sub | conn } [--help]

NanoMQ nng message proxy

start a proxy to sub NNG url and convey nng msg to qos 2 MQTT msg and send to a specific topic "nng-mqtt" of MQTT broker:

nanomq_cli nngproxy sub0 --mqtt_url "mqtt-tcp://localhost:1883" --listen "tcp://127.0.0.1:10000" -t nng-mqtt --qos 1
nanomq_cli sub -t nng-mqtt
nanomq_cli nngcat --pub --dial="tcp://127.0.0.1:10000" --data "cuckoo" --interval 1

start a proxy sub to topic "nng-mqtt" of MQTT broker, and convert MQTT msg to NNG msg, then pub to NNG url:

nanomq_cli nngcat --sub --listen="tcp://127.0.0.1:10000" -v  --quoted
nanomq_cli nngproxy pub0 --mqtt_url "mqtt-tcp://localhost:1883" --dial "tcp://127.0.0.1:10000" -t nng-mqtt --qos 0
nanomq_cli pub -t nng-mqtt -m test

Note: NanoMQ provides several ways of configurations so that user can achieve better performance on different platforms, check here for details.

Compile & Install

NanoMQ dedicates to delivering a simple but powerful Messaging Hub on various edge platforms.

With this being said, NanoMQ can run on different architectures such like x86_64 and ARM with minor migration efforts.

Docker

docker run -d -p 1883:1883 -p 8883:8883 --name nanomq emqx/nanomq:0.11.0

Building From Source

To build NanoMQ, requires a C99 compatible compiler and CMake (version 3.13 or newer).

It is recommended to compile with Ninja:

git clone https://github.com/emqx/nanomq.git ; cd nanomq
git submodule update --init --recursive
mkdir build && cd build
cmake -G Ninja ..
ninja

Or to compile without Ninja:

git clone https://github.com/emqx/nanomq.git ; cd nanomq
git submodule update --init --recursive
mkdir build && cd build
cmake .. 
make

Note (optional) build NanoMQ with QUIC bridging feature This enable NanoMQ bridging with EMQX 5.0 via MQTT over QUIC protocol

cmake -G Ninja -DNNG_ENABLE_QUIC=ON ..
ninja

Attention: MQTT over QUIC bridging requires libmsquic preinstalled, for now we do not release formal binary package with QUIC support due to compatability.

Note (optional): TLS is disabled by default. If you want to build with TLS support you will also need mbedTLS. After installing mbedTLS, you can enable it by -DNNG_ENABLE_TLS=ON.

cmake -G Ninja -DNNG_ENABLE_TLS=ON ..
ninja

Note (optional): client ( pub / sub / conn ) is built by default, you can disable it via -DBUILD_CLIENT=OFF.

cmake -G Ninja -DBUILD_CLIENT=OFF ..
ninja

Note (optional): gateway tool isn't built by default, you can enable it via -DBUILD_ZMQ_GATEWAY=ON.

cmake -G Ninja -DBUILD_ZMQ_GATEWAY=ON ..
ninja

Note (optional): bench tool isn't built by default, you can enable it via -DBUILD_BENCH=ON.

cmake -G Ninja -DBUILD_BENCH=ON ..
ninja

Note (optional): JWT dependency (for http server) isn't built by default, you can enable it via -DENABLE_JWT=ON.

cmake -G Ninja -DENABLE_JWT=ON ..
ninja

Note (optional): SQLite3 (for message persistence) isn't built by default, you can enable it via -DNNG_ENABLE_SQLITE=ON.

cmake -G Ninja -DNNG_ENABLE_SQLITE=ON ..
ninja

Note (optional): nanomq as a static lib isn't built by default, you can enable it via -DBUILD_STATIC_LIB=ON.

cmake -G Ninja -DBUILD_STATIC_LIB=ON ..
ninja libnano

Note (optional): nanomq as a shared lib isn't built by default, you can enable it via -DBUILD_SHARED_LIBS=ON.

cmake -G Ninja -DBUILD_SHARED_LIBS=ON ..
ninja

Note (optional): nanonng are dependency of NanoMQ that can be compiled independently.

To compile nanonng (nanonng is the fork of nng repository with MQTT support):

cd nng/build
cmake -G Ninja ..
ninja

Configuration

NanoMQ as an MQTT broker with good compatibility and portability, it provides several options for optimizing performance according to your system.

Compiling parameters

With CMake, NanoMQ allows user to have broker natively tuned/configured when building from source. Please kindly find the parameters as follows:

CMake Configuration

To use CMake configuration, navigating to ./nanomq/build and typing the following command :

cmake ..

Be aware that, CMake configuration is enabled by default, If you leave all parameters empty, the default value will take effect.

Limiting the number of threads by specifying the number of and the max number of taskq threads:

Recommendation: equal to your CPU cores
```
cmake -G Ninja -DNNG_NUM_TASKQ_THREADS=<num> ..
cmake -G Ninja -DNNG_MAX_TASKQ_THREADS=<num> ..
```
Setting the number of concurrent resolver threads:

Recommendation: 1
```
cmake -G Ninja -DNNG_RESOLV_CONCURRENCY=<num> ..
```
Inherited from NNG
For debugging, NanoMQ has a logging system that logs all information from all threads. Enabling or disabling the debugging messages by (Mac users should disable it before compilation):

Default: disabled (1)
```
cmake -G Ninja -DNOLOG=0  ..
cmake -G Ninja -DNOLOG=1  ..
```
Setting the logical concurrency limitation:

Default: 32
```
cmake -G Ninja -DPARALLEL=<num> ..
```

Booting Parameters

Users can also change the configuration parameters of NanoMQ while booting. However, part of the parameters is excluded in this method.

NanoMQ configuration file

NanoMQ will look up to it's configuration file in /etc/ by default. Please remember to copy conf file to /etc/ in your system if you wanna start NanoMQ without setting conf path manually. This 'nanomq.conf' allows you to configure broker when booting. Please be noted that if you start NanoMQ in the project's root directory, this file will be read automatically.

You can also write your own configuration file. Be sure to start NanoMQ in this fashion to specify an effective configuration file:

nanomq start --conf <$FILE_PATH>

Docker version: Specify config file path from host:

docker run -d -p 1883:1883 -v {YOU LOCAL PATH}: /etc \
            --name nanomq  emqx/nanomq:0.9.0

NanoMQ Environment Variables

Variable	Type	Value
NANOMQ_BROKER_URL	String	'nmq-tcp://host:port', 'tls+nmq-tcp://host:port'
NANOMQ_DAEMON	Boolean	Set nanomq as daemon (default: false).
NANOMQ_NUM_TASKQ_THREAD	Integer	Number of taskq threads used, `num` greater than 0 and less than 256.
NANOMQ_MAX_TASKQ_THREAD	Integer	Maximum number of taskq threads used, `num` greater than 0 and less than 256.
NANOMQ_PARALLEL	Long	Number of parallel.
NANOMQ_PROPERTY_SIZE	Integer	Max size for a MQTT user property.
NANOMQ_MSQ_LEN	Integer	Queue length for resending messages.
NANOMQ_QOS_DURATION	Integer	The interval of the qos timer.
NANOMQ_ALLOW_ANONYMOUS	Boolean	Allow anonymous login (default: true).
NANOMQ_WEBSOCKET_ENABLE	Boolean	Enable websocket listener (default: true).
NANOMQ_WEBSOCKET_URL	String	'nmq-ws://host:port/path', 'nmq-wss://host:port/path'
NANOMQ_HTTP_SERVER_ENABLE	Boolean	Enable http server (default: false).
NANOMQ_HTTP_SERVER_PORT	Integer	Port for http server (default: 8081).
NANOMQ_HTTP_SERVER_USERNAME	String	Http server user name for auth.
NANOMQ_HTTP_SERVER_PASSWORD	String	Http server password for auth.
NANOMQ_TLS_ENABLE	Boolean	Enable TLS connection.
NANOMQ_TLS_URL	String	'tls+nmq-tcp://host:port'.
NANOMQ_TLS_CA_CERT_PATH	String	Path to the file containing PEM-encoded CA certificates.
NANOMQ_TLS_CERT_PATH	String	Path to a file containing the user certificate.
NANOMQ_TLS_KEY_PATH	String	Path to the file containing the user's private PEM-encoded key.
NANOMQ_TLS_KEY_PASSWORD	String	String containing the user's password. Only used if the private keyfile is password-protected.
NANOMQ_TLS_VERIFY_PEER	Boolean	Verify peer certificate (default: false).
NANOMQ_TLS_FAIL_IF_NO_PEER_CERT	Boolean	Server will fail if the client does not have a certificate to send (default: false).
NANOMQ_CONF_PATH	String	NanoMQ main config file path (defalt: /etc/nanomq.conf).

Specify a broker url. On host system:

export NANOMQ_BROKER_URL="nmq-tcp://0.0.0.0:1883"
export NANOMQ_TLS_ENABLE=true
export NANOMQ_TLS_URL="tls+nmq-tcp://0.0.0.0:8883"

Creating docker container:

docker run -d -p 1883:1883 -p 8883:8883 \
           -e NANOMQ_BROKER_URL="nmq-tcp://0.0.0.0:1883" \
           -e NANOMQ_TLS_ENABLE=true \
           -e NANOMQ_TLS_URL="tls+nmq-tcp://0.0.0.0:8883" \
           --name nanomq emqx/nanomq:0.8.0

Specify a nanomq config file path. On host system:

export NANOMQ_CONF_PATH="/usr/local/etc/nanomq.conf"

Creating docker container:

docker run -d -p 1883:1883 -e NANOMQ_CONF_PATH="/usr/local/etc/nanomq.conf" \
            [-v {LOCAL PATH}:{CONTAINER PATH}] \
            --name nanomq emqx/nanomq:0.8.0

NanoMQ Command-Line Arguments

The same configuration can be achieved by adding some command-line arguments when you start NanoMQ broker. There are a few arguments for you to play with. And the general usage is:

Usage: nanomq { { start | restart [--url <url>] [--conf <path>] [-t, --tq_thread <num>]
                     [-T, -max_tq_thread <num>] [-n, --parallel <num>] 
                     [-D, --qos_duration <num>] [--http] [-p, --port] [-d, --daemon] 
                     [--cacert <path>] [-E, --cert <path>] [--key <path>] 
                     [--keypass <password>] [--verify] [--fail] }
                     | stop }

Options: 
  --url <url>                Specify listener's url: 'nmq-tcp://host:port', 
                             'tls+nmq-tcp://host:port', 
                             'nmq-ws://host:port/path', 
                             'nmq-wss://host:port/path'
  --conf <path>              The path of a specified nanomq configuration file 
  --http                     Enable http server (default: false)
  -p, --port <num>           The port of http server (default: 8081)
  -t, --tq_thread <num>      The number of taskq threads used, 
                             `num` greater than 0 and less than 256
  -T, --max_tq_thread <num>  The maximum number of taskq threads used, 
                             `num` greater than 0 and less than 256
  -n, --parallel <num>       The maximum number of outstanding requests we can handle
  -s, --property_size <num>  The max size for a MQTT user property
  -S, --msq_len <num>        The queue length for resending messages
  -D, --qos_duration <num>   The interval of the qos timer
  -d, --daemon               Run nanomq as daemon (default: false)
  --cacert                   Path to the file containing PEM-encoded CA certificates
  -E, --cert                 Path to a file containing the user certificate
  --key                      Path to the file containing the user's private PEM-encoded key
  --keypass                  String containing the user's password. 
                             Only used if the private keyfile is password-protected
  --verify                   Set verify peer certificate (default: false)
  --fail                     Server will fail if the client does not have a 
                             certificate to send (default: false)
  --log_level   <level>      The level of log output 
                             (level: trace, debug, info, warn, error, fatal)
                             (default: warn)
  --log_file    <file_path>  The path of the log file 
  --log_stdout  <true|false> Enable/Disable console log output (default: true)
  --log_syslog  <true|false> Enable/Disable syslog output (default: false)

start, restart, and stop command is mandatory as it indicates whether you want to start a new broker, or replace an existing broker with a new one, or stop a running broker;

If stop is chosen, no other arguments are needed, and an existing running broker will be stopped:
```
nanomq stop
```
All arguments are useful when start and restart are chosen. An URL is mandatory (unless an URL is specified in the 'nanomq.conf', or in your configuration file), as it indicates on which the host and port a broker is listening:
```
nanomq start|restart 					
nanomq start|restart --conf <$FILE_PATH> 
```
Telling broker that it should read your configuration file.

Be aware that command line arguments always has a higher priority than both 'nanomq.conf' and your configuration file:
```
nanomq start|restart --conf <$FILE_PATH> 
```
Running broker in daemon mode:
```
nanomq start|restart --daemon
```

Running broker with tls:

nanomq start --url "tls+nmq-tcp://0.0.0.0:8883" [--cacert <path>] [-E, --cert <path>] [--key <path>] [--keypass <password>] [--verify] [--fail]

Limiting the number of threads by specifying the number of and the max number of taskq threads:
```
nanomq start|restart  --tq_thread <num>
nanomq start|restart  --max_tq_thread <num>
```
Limiting the maximum number of logical threads:
```
nanomq start|restart --parallel <num>
```
Setting the max property size for MQTT packet:

Default: 32 bytes
```
nanomq start|restart --property_size <num>
```
Setting the queue length for a resending message: 'please be aware that this parameter also defines the upper limit of memory used by NanoMQ' 'And affect the flying window of message, please set to > 1024 if you do not want to lose message'

Default: 256
```
nanomq start|restart --msq_len <num>
```
Setting the interval of the qos timer (Also a global timer interval for session keeping):

Default: 30 seconds
```
nanomq start|restart --qos_duration <num>
```

Setting the log option:

Default: log_level=warn, log_file=none, log_stdout=true, log_syslog=false

nanomq start|restart --log_level=<level> [--log_file <file_path>] [--log_stdout <true|false>]  [--log_syslog <true|false>]

Priority: Command-Line Arguments > Environment Variables > Config files

For tuning NanoMQ according to different hardware, please check the Doc.

Community

Our Website

Visit our official website to have a good grasp on NanoMQ MQTT broker and see how it can be applied in current industries.

Test Report

This test report shows how extraordinary and competitive the NanoMQ is in Edge Computing.

Currently the benchmark is for 0.2.5, the updated one with ver 0.3.5 is coming soon

Open Source

NanoMQ is fully open-sourced!

Questions

The Github Discussions provides a place for you to ask questions and share your ideas with users around the world.

Slack

You could join us on Slack. We now share a workspace with the entire EMQ X team. After joining, find your channel!

#nanomq: is a channel for general usage, where for asking question or sharing using experience;
#nanomq-dev: is a channel for MQTT lover and developer, your great thoughts are what we love to hear;
#nanomq-nng: is a channel for guys who are interested in NNG, one of our fabulous dependencies.

Link Exchange

License

MIT License

Authors

The EMQ Edge Computing team.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

NanoMQ

Features

Quick Start

Compile & Install

Docker

Building From Source

Configuration

Compiling parameters

CMake Configuration

Booting Parameters

NanoMQ configuration file

NanoMQ Environment Variables

NanoMQ Command-Line Arguments

Community

Our Website

Test Report

Open Source

Questions

Slack

Link Exchange

MQTT Specifications

MQTT Client Examples

MQTT Client SDK

License

Authors

Files

README.md

Latest commit

History

README.md

File metadata and controls

NanoMQ

Features

Quick Start

Compile & Install

Docker

Building From Source

Configuration

Compiling parameters

CMake Configuration

Booting Parameters

NanoMQ configuration file

NanoMQ Environment Variables

NanoMQ Command-Line Arguments

Community

Our Website

Test Report

Open Source

Questions

Slack

Link Exchange

MQTT Specifications

MQTT Client Examples

MQTT Client SDK

License

Authors