MQTT服务器特性支持详情

特别提示:本人博客部分有参考网络其他博客,但均是本人亲手编写过并验证通过。如发现博客有错误,请及时提出以免误导其他人,谢谢!欢迎转载,但记得标明文章出处:http://www.cnblogs.com/mao2080/

1、列表详情

ServerQoS 0QoS 1QoS 2authbridge$SYSSSLdynamic topicsclusterwebsocketsplugin 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

posted @ 2017-11-09 14:33  mao2080  阅读(2124)  评论(0编辑  收藏  举报