Connect to the messaging channel through an adapter, client or connector.
Messaging Systems
Message Endpoint
Encapsulate the protocol-specific code that sends to or receives from a channel. The application works through an endpoint rather than directly against transport details.
How does an application connect to a messaging channel to send and receive messages?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 Endpoint works
A dedicated endpoint hides transport details from the application that sends or receives messages.
Channel
Message Endpoint
Application
Apply Message Endpoint to encapsulate delivery, consumption and transport concerns.
Expose a simpler application-facing contract and operational boundary.
What this pattern helps you decide
Encapsulate the protocol-specific code that sends to or receives from a channel. The application works through an endpoint rather than directly against transport details.
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 SDK sender/processor
- Logic Apps connectors
- BizTalk receive locations and send ports
How the analyzers can surface it
- Receive and send endpoints
- Adapter, handler and pipeline details
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.