Receive or create the message at the integration boundary.
Messaging Channels
Datatype Channel
Use a distinct channel for each message type or contract. The channel itself communicates what kind of payload consumers should expect.
How can the application send a data item such that the receiver will know how to process it?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 Datatype Channel works
The pattern introduces a clear integration responsibility between message production and consumption.
Producer
Datatype Channel
Consumer
Apply Datatype 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 distinct channel for each message type or contract. The channel itself communicates what kind of payload consumers should expect.
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
- Separate queues per contract
- Event Hub per event family
- BizTalk message-type subscriptions
How the analyzers can surface it
- Message type filters
- Contract-specific endpoints
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.