OPC UA vs MQTT: Modeling and Messaging Compared

OPC UA and MQTT are easiest to compare by role. OPC UA defines models and communication concepts for interoperable industrial information. MQTT can serve as a transport for publish-subscribe messages. This is not a like-for-like choice between two complete industrial architectures.

TL;DR: OPC UA supplies the information model and communication framework; MQTT can carry messages. OPC UA supports both ClientServer and PubSub patterns, and its PubSub variant can use MQTT as a transport. Compare the modeled information and the messaging path separately.

What Is the Difference Between OPC UA and MQTT?

OPC UA Part 1 describes OPC UA as a platform-independent framework for information modeling, secure communication, and interoperability. Its concepts include an AddressSpace, Nodes, References, Clients, Servers, Services, and Sessions.

The OPC Connect comparison treats MQTT differently: as a transport option for publish-subscribe communication. This narrower role is the central distinction. OPC UA defines how information can be represented and related; MQTT can carry messages between communication endpoints.

The comparison does not make MQTT irrelevant to OPC UA. It shows why asking only “OPC UA or MQTT?” can blur two separate questions: what gives the data its shared structure, and what carries the messages?

How Does OPC UA ClientServer Work?

In OPC UA ClientServer, a Client sends service requests to a Server, and the Server performs those services. The Server exposes an AddressSpace: the collection of information visible to its Clients. Nodes represent elements in that AddressSpace, while References express relationships between Nodes.

This model supports more than reading an isolated value. A Client can interact with a structured set of information through defined Services. OPC UA Part 1 also defines Discovery as the process by which a Client obtains Server endpoint and security information.

These are architectural concepts, not performance promises. Part 1 provides an overview; later parts specify the AddressSpace, Services, mappings, and detailed security model.

Where Does MQTT Fit With OPC UA PubSub?

OPC UA also defines a PubSub variant. Part 1 identifies Publishers, Subscribers, DataSets, DataSetMessages, NetworkMessages, and message-oriented middleware as parts of that pattern. A broker can route NetworkMessages from Publishers to Subscribers.

The OPC Connect article identifies MQTT as an option for transporting OPC UA PubSub traffic in wide-area or cloud environments. In this arrangement, MQTT is not a replacement for the OPC UA information model. OPC UA object encoding preserves the defined data relationships while the chosen transport carries the messages.

That is the bounded way to say the technologies can work together: OPC UA PubSub may use MQTT as its transport. The two sources do not establish that every MQTT deployment uses OPC UA, or that every OPC UA deployment should use MQTT.

OPC UA vs MQTT: What Can Be Compared Directly?

This table is intentionally limited. The two sources do not support general rankings for latency, throughput, implementation effort, cost, market adoption, firewall behavior, or deployment security. Those outcomes depend on specifications and deployment evidence outside this article's evidence set.

How Should You Frame an OPC UA vs MQTT Decision?

Separate the decision into two questions:

1. Does the system need OPC UA's standardized information relationships or ClientServer services? OPC UA Part 1 defines those concepts.
2. Does an OPC UA PubSub path need a message transport? The OPC Connect comparison identifies MQTT as one option.

This framing does not prescribe a plant-wide architecture. It prevents a category error: comparing OPC UA's full modeling and communication framework with one transport role as though their boundaries were identical.

For more context on OPC UA, see what OPC UA is. For a wider protocol map, see IIoT protocols compared.

FAQ

What is the difference between OPC UA and MQTT?

OPC UA defines an architecture for interoperable information modeling and communication. MQTT is a messaging transport that OPC UA PubSub can use. They therefore describe different parts of a communication solution rather than equivalent feature sets.

Can OPC UA and MQTT work together?

Yes. The OPC Foundation describes MQTT as one transport option for OPC UA PubSub. In that arrangement, OPC UA supplies the information relationships and message encoding, while MQTT carries the PubSub messages.

Is OPC UA only a client-server technology?

No. OPC UA includes both ClientServer and PubSub variants. ClientServer uses service requests and responses between clients and servers; PubSub sends DataSetMessages from publishers to subscribers, potentially through message-oriented middleware.

Does MQTT provide the same information model as OPC UA?

Not by itself. The OPC Foundation comparison treats MQTT as a transport and OPC UA as the layer that preserves standardized data relationships and object encoding. A separate payload convention is not automatically the OPC UA information model.

Conclusion

OPC UA and MQTT occupy different scopes in the two bound sources. OPC UA defines interoperable information models and supports ClientServer and PubSub communication. MQTT can transport OPC UA PubSub messages. A useful comparison keeps those roles separate and avoids unsupported claims about which technology is universally faster, cheaper, safer, or better.