[{"data":1,"prerenderedAt":71},["ShallowReactive",2],{"pattern-claim-check-pattern-cdk":3},{"id":4,"title":5,"architectureURL":6,"cleanup":7,"contributors":10,"deploy":12,"description":15,"extension":16,"framework":17,"gitHub":18,"highlight":6,"introBox":24,"language":31,"level":32,"meta":33,"patternArch":34,"resources":61,"s3URL":6,"services":6,"stem":66,"testing":67,"videoId":6,"__hash__":70},"patterns\u002Fpatterns\u002Fclaim-check-pattern-cdk.json","Implementing the claim check pattern using Amazon EventBridge Pipes.",null,{"text":8},[9],"Delete the stack: \u003Ccode>cdk delete\u003C\u002Fcode>.",[11],"content\u002Fcontributors\u002Fdominik-richter.json",{"text":13},[14],"cdk deploy","To reduce the size of the events in your event-driven application, you can temporarily remove attributes. This approach is known as the claim check pattern.","json","AWS CDK",{"template":19},{"repoURL":20,"templateURL":21,"projectFolder":22,"templateFile":23},"https:\u002F\u002Fgithub.com\u002Faws-samples\u002Fserverless-patterns\u002Ftree\u002Fmain\u002Fclaim-check-pattern-cdk","serverless-patterns\u002Fclaim-check-pattern-cdk","claim-check-pattern-cdk","src\u002Flib\u002Fclaim-check-stack.ts",{"headline":25,"text":26},"How it works",[27,28,29,30],"You split a message into a reference (“claim check”) and the associated payload. Then, you store the payload in external storage and add only the claim check to events. When you process events, you retrieve relevant parts of the payload using the claim check. For example, you can retrieve a user's name and birthday based on their userID.","The claim check pattern has two parts. First, when an event is received, you split it and store the payload elsewhere. Second, when the event is processed, you retrieve the relevant information. You can implement both aspects with a pipe.","In the first pipe, you use the enrichment to split the event, in the second to retrieve the payload. In this example Lambda is used to store the data in DynamoDB.","Using a pipe to split and retrieve messages has three advantages. First, you keep events concise as they move through the system. Second, you ensure that the event contains all relevant information when it is processed. Third, you encapsulate the complexity of splitting and retrieving within the pipe.","TypeScript","300",{},{"icon1":35,"icon2":40,"icon3":44,"icon4":48,"line1":52,"line2":56,"line3":59},{"x":36,"y":37,"service":38,"label":39},15,50,"sqs","SQS",{"x":41,"y":37,"service":42,"label":43},37,"eventbridge-pipes","EventBridge Pipes",{"x":45,"y":37,"service":46,"label":47},60,"lambda","AWS Lambda",{"x":49,"y":37,"service":50,"label":51},85,"eventbridge","Amazon EventBridge",{"from":53,"to":54,"label":55},"icon1","icon2","",{"from":54,"to":57,"label":58},"icon3","Transform",{"from":57,"to":60,"label":55},"icon4",{"bullets":62},[63],{"text":64,"link":65},"More Enterprise Integration Patterns on AWS Samples","https:\u002F\u002Fgithub.com\u002Faws-samples\u002Famazon-eventbridge-pipes-architectural-patterns","patterns\u002Fclaim-check-pattern-cdk",{"text":68},[69],"See the GitHub repo for detailed testing instructions.","SLascfkEqvioD-o1anBRjaqAUb8BVCw2hE4Rs0frjGw",1779273334221]