Receive or create the message at the integration boundary.
Messaging Systems
Message Channel
Use a logical channel as the transport boundary between producer and consumer. Channel semantics define delivery, ordering, durability and who may receive each message.
How does one application communicate with another using messaging?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 Channel works
The pattern introduces a clear integration responsibility between message production and consumption.
Producer
Message Channel
Consumer
Apply Message Channel to solve the recurring design problem.
Continue the message flow with clearer responsibilities and lower coupling.
What this pattern helps you decide
Use a logical channel as the transport boundary between producer and consumer. Channel semantics define delivery, ordering, durability and who may receive each message.
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 queue or topic
- Event Hub
- BizTalk MessageBox subscription
How the analyzers can surface it
- Adapter and endpoint inventory
- Queue/topic destinations
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.