Claim check pattern By David Boyne
Claim check pattern By David Boyne
Struggling with event-driven architecture?
You're not alone. I've seen plenty of teams start with a clean event-driven architecture only to end up with a distributed big ball of mud — broken schemas, unclear ownership, events nobody documented. There's two ways I can help:
Sometimes you may want to store information first, and then send message downstream to consumers. This allows you to offload data or large events into a database and then send lighter events downstream.
An example use-case of this pattern would be to send large payloads (exceeding your event broker limits) to downstream consumers. First you store, then you use the key downstream to get the information back from the database.
Extra resources
- Claim Check Enterprise Integration pattern - Enterprise integration pattern for claim check, if you want to know more head here.
- Publish large EventBridge events with the claim check pattern - Blog post that I wrote, to help you use the claim check pattern with Amazon EventBridge.
- Code example using S3 and EventBridge - Pattern to show you how to use S3 and EventBridge with claim check
Explore other visuals
Want to work together?
If you're interested in collaborating, I offer consulting, training, and workshops. I can support you throughout your event-driven architecture journey, from design to implementation. Feel free to reach out to discuss how we can work together, or explore my services on EventCatalog.
EDA Visuals: The book
Join over 13,000 others learning EDA and download all the EDA visuals directly to your computer.
This book contains all the visuals in one book, you can download, read offline and explore.
If you would like to support my work, you can purchase the book. This helps keeping the visuals free for the community. Purchase the book
