Features and Limitations of Various MQTT Brokers
This article documents the supported features, deprecated services, and specific limitations of a range of MQTT brokers, providing a concise reference for developers to understand each broker's capabilities and constraints within IoT and backend messaging systems.
This page records the capabilities of various MQTT servers (brokers), indicating which features each supports and noting that many offer functionality beyond the core MQTT protocol.
The "Key" legend explains the symbols used: ✔ means supported, ✘ not supported, ? unknown, § limited, and rm denotes a planned roadmap.
A list of deprecated or discontinued software/services includes 2lemetry (acquired by AWS), Apache ActiveMQ Apollo, JoramMQ, IBM Watson IoT Platform (formerly IBM IoT Gateway), mosca, RSMB (now General Messaging), and TraferoTstack (unmaintained since 2017).
The "Limitations" section outlines specific constraints such as AWS IoT retaining topics that start with "$", ClearBlade also reserving "$"‑prefixed topics, mosquitto clustering via back‑ends like Redis or AMQP, MQTT.js accepting credentials without actual verification, Software AG Universal Messaging using proprietary clustering and bridging protocols, Solace providing a proprietary broker‑to‑broker bridge, and MQTTnet offering an extensible client/server implementation primarily for .NET developers.
Architects Research Society
A daily treasure trove for architects, expanding your view and depth. We share enterprise, business, application, data, technology, and security architecture, discuss frameworks, planning, governance, standards, and implementation, and explore emerging styles such as microservices, event‑driven, micro‑frontend, big data, data warehousing, IoT, and AI architecture.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.