Back to Catalog
Integration
Message Routing
Recipient List
Send one message to multiple recipients at once — controlled multicast.
Intent & Description
Real-world Use Case
Notification dispatch — a NotificationTriggered message specifies recipientIds=[user1, user2, user5]. Recipient List router sends to email-channel, push-channel, and sms-channel based on each user’s registered preferences. Three different delivery paths from one message.
Source
📌 TL;DR
Recipient List = controlled multicast. Compute who gets the message, send a copy to each. More targeted than Pub-Sub, more flexible than point-to-point.
Advantages
- Targeted delivery — only intended recipients get the message
- More precise than Pub-Sub broadcast for dynamic recipient sets
- List can be computed at runtime from a registry or message content
- Pairs naturally with Scatter-Gather for collect-all-responses flows
Disadvantages
- N recipients = N message copies — increases broker traffic
- Recipient list computation adds latency to routing
- List registry becomes a critical dependency
- Error on one recipient delivery does not automatically retry others