OPC UA and MQTT solve different parts of an industrial information problem. OPC UA defines interoperable services, information models, security, and client-server or PubSub behavior; MQTT is a lightweight publish-subscribe transport through a broker. Many architectures use both, but only when semantics, topic governance, security, quality, and ownership are explicit.
The short answer
Use OPC UA when applications need discoverable industrial information, typed data, services, events, alarms, security profiles, and interoperable semantics. Use MQTT when decoupled publishers and subscribers need efficient brokered message distribution across intermittent or many-to-many links. MQTT does not define the meaning of an opaque payload; OPC UA PubSub can use MQTT as a transport mapping, so the technologies are not mutually exclusive.
- Start from consumers, decisions, data ownership, latency, outage, and security requirements rather than protocol popularity.
- Define information semantics, identifiers, units, quality, timestamps, sequence, and schema evolution independently of transport.
- Treat broker, certificate, identity, authorization, topic, namespace, and key-management design as production engineering.
- Test buffering, duplicates, ordering, stale data, reconnect, retained messages, and recovery end to end.
Decision guide
| Question | OPC UA emphasis | MQTT emphasis |
|---|---|---|
| What is exchanged? | Structured address space, services, events, typed data, and information models | Messages on governed topics with an application-defined payload |
| How do parties interact? | Client-server and OPC UA PubSub models | Brokered publish-subscribe model |
| Where is meaning defined? | OPC UA types, models, companion specifications, and metadata | Payload schema and topic contract selected by the application |
| What must be engineered? | Endpoints, profiles, certificates, trust, namespaces, subscriptions, and models | Broker topology, sessions, QoS, topics, retained data, payload schema, identity, and ACLs |
A practical workflow
- 01
List producers, consumers, required decisions, latency, volumes, connectivity, retention, and failure behavior.
- 02
Define the canonical information model, identifiers, units, timestamps, quality, ownership, and versioning.
- 03
Choose interaction patterns per interface instead of imposing one protocol on the entire architecture.
- 04
Design certificates, trust, broker or endpoint authorization, network conduits, monitoring, renewal, and incident recovery.
- 05
Test normal and abnormal message behavior, reconnect, duplicates, ordering, stale data, schema change, load, and reconciliation.
Evidence and acceptance
Retain the interface contract, namespace and topic rules, payload schemas, certificate and trust design, supported profiles and versions, quality mapping, timeout and retry behavior, load results, cybersecurity review, failure tests, and consumer reconciliation. An interface is accepted only when both ends interpret the same data and recover predictably.
Common mistakes
- Calling MQTT a semantic model or assuming topic names alone make payloads interoperable.
- Treating OPC UA as one fixed wire protocol while ignoring profiles, security modes, models, and supported services.
- Bridging operational data to enterprise networks without segmentation, least privilege, rate limits, and ownership.
- Ignoring certificate lifecycle, broker persistence, offline buffering, duplicate delivery, and schema compatibility.
- Validating only a live happy path instead of loss, delay, restart, renewal, and recovery conditions.
Engineering and security boundary
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
Does MQTT replace OPC UA?
Not generally. MQTT provides brokered messaging; OPC UA provides a broader interoperability framework including information modeling, services, security, and PubSub. The required architecture may use either or both.
Can OPC UA PubSub use MQTT?
Yes. OPC UA Part 14 defines PubSub communication and transport mappings that include MQTT, allowing OPC UA-defined dataset messages to travel through an MQTT broker.
Which MQTT QoS should an industrial project use?
Choose from the application’s loss, duplication, latency, bandwidth, and reconciliation requirements. QoS does not replace application-level identity, timestamps, quality, sequence, or validation.
Does AutoNexit transfer process data?
No. It preserves architecture records and acceptance evidence; runtime platforms perform the actual industrial communications.