Millions of Events per Minute During a World Cup, No Big Deal!
summary
An architecture for handling massive event volumes during the World Cup using AWS services: SNS, SQS, Lambda, Fargate and EFS for durable buffering, with Vector for reliable publishing and Kinesis → S3 as the data lake. It describes an event-first pipeline that processed billions of messages and consumptions, uses AsyncAPI and custom client libraries for contracts, and relies on serverless autoscaling plus dead‑letter replay Lambdas; SNS limitations (loss, no native replay/registry) required EFS buffering and manual contract tooling.
AI-written summary · about
chapters (6)
- 0:00Start
- 20:25Technical requirements
- 27:49Consumption Architecture
- 30:26State of requirements
- 32:48At least one delivery
- 35:25Error recovery and analysis capabilities
related talks
49mBuilding Next-Generation Applications with EDA
45mBuilding Event-driven Serverless Applications
57mLessons in Building a System that Processes More than 70 Billion Events Daily
38mEvent-driven Architecture
39mBuilding next-gen applications with event-driven architecture
29mEvent streaming with modern data pipelines in a SaaS architecture
41mGetting started with Event-Driven Architectures in 2023
51mServerless architectural patterns