The Road To Event-Driven Architecture At
summary
LEGO.com moves from a 2016 JBoss monolith to serverless by 2018, building 15–18 pipelines with Lambda, Kinesis for streams and later AWS EventBridge and Step Functions to tame choreography vs orchestration. The team adopts on‑demand migration instead of mass data moves, handles millions of events in streaming, isolates third‑party integrations and distills domains into smaller deployable pieces. Result: autonomous product squads replace slow releases, scaling works in production, observability improves and the approach proves practical and repeatable.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:142 common questions
- 2:43LEGO high-level architecture
- 4:36The runway to EDA
- 5:29Monolith Days 2016
- 8:38Future thinking
- 12:16The first step
- 14:14EDA phase 1
- 17:38EDA phase 2
- 23:44Microservices
- 33:18Set-piece case study
- 45:15Experience
- 49:00Wrap-up
- 49:26Outro
related talks
56mArchitectural Patterns in the Serverless Journey of shop.LEGO.com
42mEnterprise Serverless Adoption. An Experience Report
30mEvolving Serverless Architectures
38mEvent-driven Architecture
45mBuilding Event-driven Serverless Applications
37mBuild next-gen applications with event-driven architectures
01h 02mServerless in production, an experience report
47mServerless in production, an experience report
