Industrial MQTT topic design: names, payloads and data contracts
Design a stable telemetry namespace with identity, timestamps, units, quality and schema ownership before connecting dashboards and consumers.
MQTT delivery guarantees: 0, 1, or 2.
MQTT quality of service: QoS 0 (at most once), QoS 1 (at least once, may duplicate), QoS 2 (exactly once). Negotiated per hop and capped by the subscription — publishing high to a low-QoS subscriber still delivers at most once.
See also: MQTT · Sparkplug B
Use the concept: Industrial data connectivity: from register to consumer · Industrial data contract template
Design a stable telemetry namespace with identity, timestamps, units, quality and schema ownership before connecting dashboards and consumers.
The decisions that matter before an MQTT edge gateway leaves the lab: protocol drivers, buffering, namespaces, quality, security, and ownership.
Star, line, ring, and redundant designs explained through failure modes, commissioning effort, latency, and the maintenance team’s real needs.