MQTT服務器特性支持詳情


特別提示:本人博客部分有參考網絡其他博客,但均是本人親手編寫過並驗證通過。如發現博客有錯誤,請及時提出以免誤導其他人,謝謝!歡迎轉載,但記得標明文章出處: http://www.cnblogs.com/mao2080/

1、列表詳情

Server QoS 0 QoS 1 QoS 2 auth bridge $SYS SSL dynamic topics cluster websockets plugin system
Trafero Tstack
mosquitto §
RSMB ?
WebSphere MQ ? ? ?
HiveMQ
Apache Apollo ? ?
Apache ActiveMQ
Software AG Universal Messaging rm
RabbitMQ ? ? ?
Solace §
MQTT.js §
moquette ? ? ? rm
mosca ? ? ? ?
IBM MessageSight §
2lemetry §
GnatMQ
JoramMQ
VerneMQ
emqttd
HBMQTT
Mongoose ? ? ? ? ? ? ? ? ?
emitter §
Bevywise IoT Platform rm rm

     Key: ✔ supported ✘ not supported ? unknown § see limitations rm roadmap (planned)

     Limitations

  • MQTT.js will accept connections with username and password supplied, but do not actually authenticate the connection

  • IBM MessageSight supports a High-Availability mode which provides the redundancy advantage of a cluster, but does not support any sort of load balancing for MQTT.

  • 2lemetry uses domains, where the first topic segment is the domain name. The $SYS topic space is under the domain (i.e. com.example/$SYS/#)

  • Solace does provide a proprietary bridge solution between brokers.

  • mosquitto clustering is achieved on backend level (redis, amqp, etc).

  • Software AG Universal Messaging provides Active/Active clustering (over a proprietary protocol) and bridging (over a proprietary protocol).

Potentially should add columns to track: LWT; additional protocols (WMQ, AMQP, MQTTs etc)

2、參考網站

https://github.com/mqtt/mqtt.github.io/wiki/server-support


免責聲明!

本站轉載的文章為個人學習借鑒使用,本站對版權不負任何法律責任。如果侵犯了您的隱私權益,請聯系本站郵箱yoyou2525@163.com刪除。



 
粵ICP備18138465號   © 2018-2025 CODEPRJ.COM