Claim Checks at Scale: Stop Letting Every Consumer Talk to S3

Previously during the Advent of EIP I covered the Claim Check Pattern as part of Day 5: Message Types & Event Payload Strategies. In that write up I left the implementation purposefully simple: write the document to S3 and include the S3 address in the payload for the consuming side to receive and fetch the bytes. This is a pattern I have used time and time again and it works well regardless of whatever object store you use and is very simple for your team to reason about.