Identify the payload or state that must survive beyond the current processing attempt.
Messaging Channels
Guaranteed Delivery
Persist messages so infrastructure failures do not silently lose them. Delivery guarantees still require idempotent consumers and explicit failure handling.
How can the sender make sure that a message will be delivered, even if the messaging system fails?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 Guaranteed Delivery works
The integration persists data or processing state so it can be recovered, deduplicated or retrieved later.
Message or payload
Guaranteed Delivery
Durable reference / state
Apply Guaranteed Delivery 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
Persist messages so infrastructure failures do not silently lose them. Delivery guarantees still require idempotent consumers and explicit failure handling.
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 entities
- Peek-lock processing
- BizTalk durable MessageBox
How the analyzers can surface it
- Retry settings
- Durability and delivery 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.