Claim-Check Pattern¶
Keep large payloads in object storage and send a small, verifiable reference through the broker.
flowchart LR
J[Junior: why offload] --> M[Middle: how claims work] --> S[Senior: lifecycle failures] --> P[Professional: storage scale]
flowchart LR
Producer --> Blob[(Object storage)]
Producer --> Claim[Broker claim] --> Consumer --> Blob
| Level | Guide | You are done when |
|---|---|---|
| Junior | Definition and why | You can explain payload offload and orphan risk. |
| Middle | How it works | You can publish and verify an immutable claim. |
| Senior | Failures and mistakes | You can make retention and replay safe. |
| Professional | Best practices and scale | You can operate integrity and garbage collection. |
Practice rule: Publish only durable claims and delete only unreachable blobs.