Accept one message from the producer.
Message Routing
Recipient List
Determine a set of recipients and send a copy to each one. The recipient list can be calculated from content, configuration or runtime context.
How do we route a message to a list of dynamically specified recipients?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 Recipient List works
The same message or request is distributed to multiple destinations.
Incoming message
Recipient List
Destination A
Destination B
Destination C
Apply Recipient List to select or fan out to multiple recipients.
Each recipient receives its own delivery or processing opportunity.
What this pattern helps you decide
Determine a set of recipients and send a copy to each one. The recipient list can be calculated from content, configuration or runtime context.
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 topic subscriptions
- Logic Apps foreach destinations
- BizTalk dynamic destinations
How the analyzers can surface it
- Fan-out and multiple send targets
- Dynamic recipient properties
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.