Inspect message content, metadata, state or routing configuration.
Message Routing
Dynamic Router
Let recipients advertise capabilities and make routing decisions from runtime state rather than a fixed destination list.
How can you avoid the dependency of the router on all possible destinations while maintaining its efficiency?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 Dynamic Router works
A routing decision sends the message along one of several possible paths.
Incoming message
Dynamic Router
Route A
Route B
Fallback
Use Dynamic 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
Let recipients advertise capabilities and make routing decisions from runtime state rather than a fixed destination list.
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
- Configuration-driven Function router
- Service discovery plus Service Bus
- Rules stored in App Configuration
How the analyzers can surface it
- Runtime destination expressions
- Dynamic send ports
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.