Receive or create the message at the integration boundary.
Message Construction
Command Message
Represent a request to perform an action as a message. The receiver interprets the message as an instruction rather than merely as data or notification.
How can messaging be used to invoke a procedure in another application?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 Command Message works
The pattern introduces a clear integration responsibility between message production and consumption.
Producer
Command Message
Consumer
Apply Command Message to solve the recurring design problem.
Continue the message flow with clearer responsibilities and lower coupling.
What this pattern helps you decide
Represent a request to perform an action as a message. The receiver interprets the message as an instruction rather than merely as data or notification.
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 command queue
- Durable Functions activity request
- BizTalk request message
How the analyzers can surface it
- Operation-oriented message contracts
- Request/reply 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.