Identify the payload or state that must survive beyond the current processing attempt.
Messaging Endpoints
Durable Subscriber
Keep a persistent subscription and retain events while the consumer is offline, allowing it to resume without losing relevant messages.
How can a subscriber avoid missing messages while it’s not listening for them?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 Durable Subscriber works
The integration persists data or processing state so it can be recovered, deduplicated or retrieved later.
Message or payload
Durable Subscriber
Durable reference / state
Apply Durable Subscriber to persist, reference or verify that state.
Retrieve or reuse the stored information when the flow continues or recovers.
What this pattern helps you decide
Keep a persistent subscription and retain events while the consumer is offline, allowing it to resume without losing relevant messages.
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
- Durable Service Bus subscription
- Event Hubs checkpointed consumer
- Persistent broker subscription
How the analyzers can surface it
- Subscription durability
- Checkpoint and retention configuration
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.