AiVibeMQTT Broker
An MQTT broker is the server at the centre of an MQTT system that accepts client connections, authenticates them, receives published messages and routes each message to every client subscribed to a matching topic.
Clients never communicate directly with each other in MQTT; every message passes through the broker. The broker maintains client sessions, subscriptions, retained messages and queued messages for disconnected clients with persistent sessions, and it carries out the quality-of-service handshakes. It evaluates wildcard subscriptions against each published topic, publishes last will messages when clients disconnect unexpectedly and applies access control lists that restrict which topics each client may publish or subscribe to.
In IIoT architectures, brokers run on edge gateways, on-premises servers or cloud services, and often form the hub of a unified namespace where machines, MES, historians and analytics exchange data. Open-source and commercial brokers are widely available, and many cloud IoT platforms provide managed MQTT endpoints. Bridging connects brokers at different levels, for example forwarding selected topics from a plant broker to an enterprise broker.
Because all data flows through it, the broker needs high availability through clustering or redundancy, capacity planning for connections and message rates, monitoring and secure configuration. TLS, client certificates or credentials and least-privilege topic permissions are essential, and anonymous access should be disabled in production. Broker placement should respect OT network segmentation, so that external systems never connect directly into control networks.
Key points
- Central server that routes MQTT messages from publishers to subscribers
- Keeps sessions, subscriptions, retained messages and queued messages
- Enforces authentication and topic-level access control
- Bridging links plant, site and enterprise brokers
- Needs high availability, monitoring and secure configuration
Where AiVibe comes in
AiAmbA IoT is AiVibe's edge protocol layer: it discovers devices and normalises industrial signals, with supported protocols including Siemens S7, Mitsubishi MC, Delta Modbus, OPC UA and MQTT, and driver availability confirmed per installation. Writes to machines are deny-by-default.
Related terms
- MQTTIndustrial IoT & Edge
- Unified Namespace (UNS)Industrial IoT & Edge
- MQTT Topics and WildcardsIndustrial IoT & Edge
- MQTT Quality of Service (QoS)Industrial IoT & Edge
- Edge ComputingIndustrial IoT & Edge
- IEC 62443 (ISA/IEC 62443)OT & Industrial Cybersecurity