Glossary · System coordination, integration and orchestration
Integration broker
Also known as: message broker (integration), integration hub
German: Integrationsbroker
In systems integration, an integration broker is a middleware component that mediates between applications by receiving messages, transforming and routing them, and delivering them to target applications, following a hub-and-spoke model.
- System integration
In one sentence
An integration broker receives, transforms and routes messages between applications as a central hub in a hub-and-spoke integration model.
Example
The integration broker receives quality results from the lab system, maps them to the MES format and forwards them only for batches that are still in production.
How it applies
- Architecture: A broker removes direct dependencies between applications: each connects only to the broker. The broker becomes critical infrastructure and needs availability measures.
- Engineering: Keep mappings and routing rules versioned and tested. Define error handling for messages that cannot be transformed or delivered, including who is notified.
- Documentation: Document every flow through the broker with its source, target, mapping and error handling. Support documentation should explain how to find and reprocess failed messages.
Integration broker vs. event broker
An Event broker distributes events, usually without changing them. An integration broker actively transforms and routes messages between applications with different formats. Both are often used side by side, and the documentation should make clear which flows pass through which component and why.