In PubSubthe participating OPC UA Applicationswith their roles as Publishersand Subscribersare decoupled. The number of Subscribersreceiving data from a Publisherdoes not influence the Publisher. This makes PubSubsuitable for applications where location independence and/or scalability are required.

The following are some example uses for PubSub:

  • Configurable peer to peer communication between controllers and between controllers and HMIs. The peers are not directly connected and do not even need to know about the existence of each other. The data exchange often requires a fixed time-window; it may be point-to-point connection or data distribution to many receivers.
  • Asynchronous workflows. For example, an order processing application can place an order on a message queue or an enterprise service bus. From there it can be processed by one or more workers.
  • Logging to multiple systems. For example, sensors or actuators can write logs to a monitoring system, an HMI, an archive application for later querying, and so on.
  • OPC UA Serversrepresenting services or devices can stream data to applications hosted in the cloud. For example, backend servers, big data analytics for system optimization and predictive maintenance.