Identify the payload or state that must survive beyond the current processing attempt.
Message Transformation
Claim Check
Store bulky content externally and send a small claim token that authorized consumers can use to retrieve the full payload.
How can we reduce the data volume of message sent across the system without sacrificing information content?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 Claim Check works
The integration persists data or processing state so it can be recovered, deduplicated or retrieved later.
Message or payload
Claim Check
Durable reference / state
Apply Claim Check 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
Store bulky content externally and send a small claim token that authorized consumers can use to retrieve the full payload.
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
- Claim-check pattern with Blob Storage
- Service Bus message referencing a blob
- Large-file manifest
How the analyzers can surface it
- Blob or URI references in messages
- Large payload mitigation
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.