Inspect message content, metadata, state or routing configuration.
Messaging Systems
Message Router
Insert routing logic that chooses one or more destinations without changing the message body. Centralizing the decision keeps producers and consumers unaware of each other.
How can you decouple individual processing steps so that messages can be passed to different filters depending on a set of conditions?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 Router works
A routing decision sends the message along one of several possible paths.
Incoming message
Message Router
Route A
Route B
Fallback
Use Message Router 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
Insert routing logic that chooses one or more destinations without changing the message body. Centralizing the decision keeps producers and consumers unaware of each other.
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
- APIM choose/when
- Logic Apps conditions and switches
- Service Bus subscription rules
How the analyzers can surface it
- APIM choose branches
- BizTalk send-port filters
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.