Receive or create the message at the integration boundary.
Messaging Endpoints
Message Dispatcher
Use a dispatcher to receive from one channel and assign each message to an appropriate local performer or worker.
How can multiple consumers on a single channel coordinate their message processing?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 Dispatcher works
The pattern introduces a clear integration responsibility between message production and consumption.
Producer
Message Dispatcher
Consumer
Apply Message Dispatcher to solve the recurring design problem.
Continue the message flow with clearer responsibilities and lower coupling.
What this pattern helps you decide
Use a dispatcher to receive from one channel and assign each message to an appropriate local performer or worker.
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
- Function dispatcher with worker handlers
- Host process dispatch loop
- BizTalk receive host dispatch
How the analyzers can surface it
- Single channel with multiple local handlers
- Handler and host relationships
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.