EMQX
| Developer(s) | EMQ Technologies Co., Ltd. |
|---|---|
| Stable release | v4.2.4[1]
|
| Repository | https://github.com/emqx/emqx |
| Written in | Erlang |
| Engine | |
| Operating system | Cross-platform software |
| Type | Message broker |
| License | Apache 2.0 |
| Website | https://www.emqx.io/ |
Search EMQX on Amazon.
EMQX is a fully open-source distributed MQTT messaging broker for IoT, M2M, and mobile applications. It is based on the Erlang/OTP platform and is licensed under Apache 2.0 for accessing various devices that support the MQTT protocol, for messaging from the device side to the broker side, and for forwarding device control messages from the broker side to the device side.[2]
Starting from the 3.0 release, EMQX 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.[3]
History[edit]
In 2013, EMQX was posted on GitHub as an open-source project, originally named emqtt. The project renamed EMQX after the release of version 3.0. In 2017, the team established EMQ[4], and EMQX became its commercial product. Today, EMQX has been developed as one of the most popular open-source MQTT message broker in IoT.[5] [6] [7]
Features[edit]
EMQ is infrastructure software that utilizes for IoT application development and platform establishment. In the edge and cloud end, it provides IoT device access, protocol management, message routing, data storage, streaming data processing, and other core functions, the main features as follows.
- Multiple IoT protocol support. It supports MQTT V5.0 protocol specification and is compatible with MQTT V3.1 and V3.1.1, and can also extend support for MQTT-SN, CoAP, LwM2M, WebSocket, STOMP, or private TCP and other IoT protocols.[8] [9]
- Multi-language extension. The Multilingual Extended Protocol Access module allows other programming languages (such as Python, Java, etc.) to directly process byte data messages to achieve custom protocol analysis and provides Pub/Sub interfaces to achieve message exchange with the system.[10]
- Rule Engine Integration. Used to configure EMQX message flow and device event processing and response rules, reduces the coupling between the business system and EMQX.[11]
- Release Hot upgrade. Avoid the decrease in system availability caused by restarting the service.[12]
- Extensible Plugins. Can write custom plugins to support proprietary protocols at the TCP/UDP layer, store data into a database, or integrate with an external system.[13]
- Fully Open Source. EMQX is open-source software and licensed under the Apache License Version 2.0.[14]
Installation[edit]
The EMQX is cross-platform, which supports Linux, Unix, macOS and Windows. It means EMQX can be deployed on x86_64 architecture servers and ARM devices like Raspberry Pi.
Installing via EMQX Docker Image
docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8883:8883 -p 8084:8084 -p 18083:18083 emqx/emqx
One-click installation of shell script (Linux)
curl https://repos.emqx.io/install_emqx.sh | bash
References[edit]
- ↑ "EMQX v4.2.4 Release Notes". GitHub.
- ↑ "EMQX Official Website". emqx.io.
- ↑ "EMQ X 3.0-Beta.1 "Promises of Tomorrow" Released". GitHub.
- ↑ "EMQ Technologies". Crunchbase.
- ↑ "MQTT Software". mqtt.org.
- ↑ "Awesome IoT". Github.
- ↑ "The Top 18 Mqtt Broker Open Source Projects". Awesome Open Source.
- ↑ "EMQX GitHub". GitHub.
- ↑ "EMQX Introduction". EMQX Documentations.
- ↑ "Multi-language extension". EMQX Documentations.
- ↑ "Rule Engine". EMQX Documentations.
- ↑ "Release Hot upgrade". EMQX Documentations.
- ↑ "Plugins". EMQX Documentations.
- ↑ "EMQX LICENSE". GitHub.
This article "EMQX" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:EMQX. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
