Micro-frontends: a migration story on the Edge
summary
DAZN migrates a monolithic frontend to micro-frontends worldwide with more than 100 people and ~200–300 engineers involved, using AWS Lambda@Edge, CloudFront, S3 and Route 53 to implement the strangler pattern plus blue/green and canary rollouts. Configuration lives on an external CDN to keep average impact ~2 ms latency; deployment to all edges takes under 10 minutes, concurrent Lambda@Edge limit is ~1000 (requestable to 5000), traffic is sticky via cookies, and monthly edge requests hit ~300–400M costing roughly 500–750.
AI-written summary · about
chapters (14)
- 0:00Micro-frontends migration intro
- 1:01Migration context
- 7:25Core problem with two apps
- 10:34Monolith to micro-frontends
- 14:27Solution requirements
- 16:55Lambda@Edge solution
- 21:10Lambda@Edge challenges
- 23:19Lambda@Edge costs & performance
- 24:22Lambda@Edge architecture fit
- 26:13Canary & strangler patterns
- 28:20External config storage
- 30:06Multi-layer caching optimization
- 30:47Sticky sessions for consistency
- 31:08Key takeaways & future
related talks
59mMicro-Frontends in AWS
33mMicro Frontends, Five Years After
36mMicro-frontends discovery
37mDemystifying Micro-Frontends
26mScaling Applications with Microfrontends
21mMicro-frontends: 3 years ago
20mTransform Your Web App: Microfrontends & AWS Serverless
25mMicro Frontend: a microservice architecture from your frontend web apps