Skip to content
Art2link ESB v2.02 LTS HomeDocumentationBlogContact
Patterns/Transformation/Claim check

Claim check

Check the heavy luggage and carry the ticket. A large payload is stored once in external storage; the message on the bus holds only a reference token, and the payload is reclaimed by token wherever it is actually needed.

Some payloads — a scanned document, a multi-megabyte export, a media file — are expensive to carry through every routing and tracking step. The claim check stores the payload at the edge, replaces it with a small token in the canonical message, and lets that lightweight message route freely. The send port that finally delivers re-fetches the payload by its token.

large payload 10 MB doc Check in store + tokenise blob storage token on bus ref=abc123 Send port reclaim by token

The bus stays fast and its tracking readable, because routing decisions and audit records deal in small messages. For payloads too large even to check in as one blob, combine this with streaming so the data never has to sit in memory whole.

In Art2link this is not a pattern you build or a switch you flip — it is the platform’s default behaviour. Art2link evaluates the size of every payload as it passes through, and any payload above a set threshold is automatically checked into temporary Azure blob storage, carried on the bus as a token, and reclaimed where it is consumed.

Already handled — nothing for you to do. You do not configure, trigger, or clean up after the claim check. Art2link sizes each payload automatically, moves anything over the threshold into temporary Azure blob storage, and holds it there until the message is consumed or terminated — then releases it. The token’s lifetime is managed for you. Large payloads simply work, and you never have to think about it.