EMQ X broker is a fully open source, highly scalable, highly available distributed MQTT messaging broker for IoT, M2M and Mobile applications that can handle tens of millions of concurrent clients.
Starting from 3.0 release, EMQ X broker fully supports MQTT V5.0 protocol specifications and backward compatible with MQTT V3.1 and V3.1.1, as well as other communication protocols such as MQTT-SN, CoAP, LwM2M, WebSocket and STOMP. The 3.0 release of the EMQ X broker can scaled to 10+ million concurrent MQTT connections on one cluster.
The EMQ X broker is cross-platform, which supports Linux, Unix, macOS and Windows. It means EMQ X can be deployed on x86_64 architecture servers and ARM devices like Raspberry Pi.
See more details for building and running EMQ X on Windows in Windows.md
docker run -d --name emqx -p 1883:1883 -p 8081:8081 -p 8083:8083 -p 8883:8883 -p 8084:8084 -p 18083:18083 emqx/emqx
Get the binary package of the corresponding OS from EMQ X Download page.
The EMQ X broker requires Erlang/OTP R21+ to build since 3.0 release.
For 4.3 and later versions.
git clone https://github.com/emqx/emqx.git cd emqx make _build/emqx/rel/emqx/bin console
For earlier versions, release has to be built from another repo.
git clone https://github.com/emqx/emqx-rel.git cd emqx-rel make _build/emqx/rel/emqx/bin/emqx console
If emqx is built from source,
Or change to the installation root directory if emqx is installed from a release package.
# Start emqx ./bin/emqx start # Check Status ./bin/emqx_ctl status # Stop emqx ./bin/emqx stop
To view the dashboard after running, use your browser to open: http://localhost:18083
make eunit ct
DIALYZER_ANALYSE_APP=emqx_lwm2m,emqx_authz make dialyzer
Visiting EMQ X FAQ to get help of common problems.
GitHub Discussions is where you can ask questions, and share ideas.
For more organised improvement proposals, you can send pull requests to EIP.
To develop your own plugins, see lib-extra/README.md
You can read the mqtt protocol via the following links:
Apache License 2.0, see LICENSE.
：Code submit frequency
：React/respond to issue & PR etc.
：Well-balanced team members and collaboration
：Recent popularity of project
：Star counts, download counts etc.