Connect to the messaging channel through an adapter, client or connector.
Messaging Endpoints
Selective Consumer
Apply selection criteria at the consumer or subscription so only matching messages are delivered to that endpoint.
How can a message consumer select which messages it wishes to receive?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 Selective Consumer works
A dedicated endpoint hides transport details from the application that sends or receives messages.
Channel
Selective Consumer
Application
Apply Selective Consumer to encapsulate delivery, consumption and transport concerns.
Expose a simpler application-facing contract and operational boundary.
What this pattern helps you decide
Apply selection criteria at the consumer or subscription so only matching messages are delivered to that endpoint.
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 subscription rules
- JMS selector
- BizTalk send-port filter
How the analyzers can surface it
- BizTalk filter expressions
- Subscription criteria
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.