Receive or create the message at the integration boundary.
Messaging Channels
Message Bus
Standardize channels, contracts and adapters around a shared messaging backbone so applications can join or leave with limited point-to-point coupling.
What is an architecture that enables separate applications to work together, but in a decoupled fashion such that applications can be easily added or removed without affecting the others?Adapted from Enterprise Integration Patterns under CC BY 3.0. The visualization and explanatory content on this page are original GateSift material.
Original GateSift visualization
How Message Bus works
The pattern introduces a clear integration responsibility between message production and consumption.
Producer
Message Bus
Consumer
Apply Message Bus to solve the recurring design problem.
Continue the message flow with clearer responsibilities and lower coupling.
What this pattern helps you decide
Standardize channels, contracts and adapters around a shared messaging backbone so applications can join or leave with limited point-to-point coupling.
What happens when processing fails or the same message is delivered twice?
Where does state, correlation or routing configuration live?
How will operators trace the message and understand the decision path?
Where you may see it
- Service Bus namespace with governance
- Enterprise event backbone
- BizTalk MessageBox architecture
How the analyzers can surface it
- Shared channel and contract dependencies
- Central routing and adapter inventory
Pattern detection is contextual. GateSift should present these as architectural signals, not claim a pattern is implemented solely because one policy statement or adapter exists.
Source, licence and attribution
The pattern name and selected problem statement are adapted from Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf under CC BY 3.0. GateSift summaries, Azure mappings, analyzer guidance and diagrams are original. No endorsement by the original authors is implied.