Accept one message from the producer.
Messaging Channels
Publish-Subscribe Channel
Publish once to a channel that fans the event out to every interested subscription. Producers remain unaware of how many consumers exist.
How can the sender broadcast an event to all interested receivers?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 Publish-Subscribe Channel works
The same message or request is distributed to multiple destinations.
Incoming message
Publish-Subscribe Channel
Destination A
Destination B
Destination C
Apply Publish-Subscribe Channel to select or fan out to multiple recipients.
Each recipient receives its own delivery or processing opportunity.
What this pattern helps you decide
Publish once to a channel that fans the event out to every interested subscription. Producers remain unaware of how many consumers exist.
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 topics and subscriptions
- Event Grid topics
- Event Hubs consumer groups
How the analyzers can surface it
- Topic and subscription destinations
- Fan-out routing
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.