Advanced Event-driven Architectures at
summary
LEGO’s backend uses Kinesis Firehose to S3 with 1 MB / 60 s buffering and 5‑day S3 lifecycle, a Lambda triage that fans events to domains, and EventBridge + API Destinations to push transformed events to HTTP endpoints (demo shows user agent "API destinations"). Payments handle peaks — ~1,000 orders, ~200,000 API requests, ~150 concurrent Lambdas — by pushing async status updates to the frontend. Cross‑service orchestration uses Step Functions task token patterns with a Lambda to call SendTaskSuccess; demos show the flow completing end to end.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:23Agenda
- 1:50Squad setups
- 3:49How to decouple squads
- 8:48Streaming events
- 14:01Demo: Event streaming
- 20:03EventBridge
- 24:04API destinations
- 25:26Demo: API Destinations
- 29:45Orchestration
- 35:00Demo: Task tokens
- 40:32Benefits of event-driven patterns
- 42:38Wrap-up
- 43:19Outro
related talks
56mArchitectural Patterns in the Serverless Journey of shop.LEGO.com
38mEvent-driven Architecture
45mBuilding Event-driven Serverless Applications
30mEvolving Serverless Architectures
52mServerless Compute at the Heart of Your EDA
49mBuilding Next-Generation Applications with EDA
23mSimplifying design complexities using Serverless Architecture on AWS
33mAWS Lambda - Logic in the Cloud without Back-end