Receive or create the message at the integration boundary.
Message Construction
Document Message
Send a business document or data structure whose content matters more than immediate timing. The receiver decides how to process the transferred information.
How can messaging be used to transfer data between applications?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 Document Message works
The pattern introduces a clear integration responsibility between message production and consumption.
Producer
Document Message
Consumer
Apply Document Message to solve the recurring design problem.
Continue the message flow with clearer responsibilities and lower coupling.
What this pattern helps you decide
Send a business document or data structure whose content matters more than immediate timing. The receiver decides how to process the transferred information.
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
- Order or customer document on Service Bus
- EDI document
- BizTalk canonical message
How the analyzers can surface it
- Schema and message-type inventory
- Document transformations
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.