Inspect message content, metadata, state or routing configuration.
Message Routing
Message Broker
Place a broker between participants to route, transform and govern messages while shielding senders from destination-specific details.
How can you decouple the destination of a message from the sender and maintain central control over the flow of messages?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 Broker works
A routing decision sends the message along one of several possible paths.
Incoming message
Message Broker
Route A
Route B
Fallback
Use Message Broker to select the next destination or processing step.
Continue on the selected path while keeping the producer decoupled from destinations.
What this pattern helps you decide
Place a broker between participants to route, transform and govern messages while shielding senders from destination-specific details.
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
- Azure Integration Services hub
- Service Bus plus Functions
- BizTalk Server
How the analyzers can surface it
- Central adapter and route inventory
- Cross-application mappings
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.