Demystifying Micro-Frontends
summary
Claim: splitting the UI into business-subdomain micro-frontends lets independent teams ship safely and scale engineering. Implementation uses an HTML-first entry, a tiny bootstrap app shell that loads one micro-frontend at a time, S3 + CloudFront for artifacts and Lambda@Edge for canary traffic, and embraces Webpack 5 module federation for shared deps. Result: five micro-frontends on DAZN, teams onboard in a week, tech org grows to ~350, company to 2,600, and production hits 10 releases per month with far fewer incidents.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 3:11What are micro-frontends
- 7:22Zone’s micro-frontend setup
- 10:13Bootstrap architecture explained
- 15:37Bootstrap responsibilities
- 17:24Loading micro-frontends dynamically
- 19:11Components vs micro-frontends
- 21:38Benefits and team scaling
- 23:24Q&A and key takeaways
related talks
32mYou don't know Microfrontends
10mMicrofrontends done right
27mMicro Frontends: Break Up You Web App!
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
29mMicro Frontends, how to evolve to an extensible frontend
26mScaling Applications with Microfrontends
45mMicro Frontends in Action!
22mMicro Frontends & me, a love story