Glossary · Automation software engineering and architecture
Message-oriented architecture
Also known as: Message-oriented middleware architecture, Messaging architecture
German: Nachrichtenorientierte Architektur
In software architecture, a message-oriented architecture is a style in which components communicate by exchanging asynchronous messages through queues or a broker instead of calling each other directly.
- Software engineering
In one sentence
A message-oriented architecture lets components communicate through asynchronous messages via queues or brokers instead of direct calls.
Example
In the plant, machine controllers, the quality system and the MES exchange events through a message broker, so a new analytics service can subscribe without changing the machines.
How it applies
- Engineering: Messaging supports Loose coupling: senders need not know receivers, and components can be added or restarted independently. The cost is added infrastructure (Middleware, brokers) and eventual rather than immediate delivery.
- Integration: Message formats become the real interfaces. A shared Serialization format and Schema validation keep producers and consumers compatible.
- Documentation: Document each message type like an API: topic or queue name, payload schema, units, versioning and delivery guarantees. Diagrams of message flows help readers more than component lists.
Message-oriented vs. request-response
In the Request-response pattern the caller waits for an answer; in a message-oriented architecture the sender continues and results, if any, arrive as further messages.