You don't know Microfrontends
summary
Claim: splitting the frontend by domain into independently deployable single-page apps actually scales teams and platforms. Implementation: bootstrap is a tiny index.html with vanilla JS that handles routing and lifecycle while one microfrontend loads at a time, pure SPA per team. Built features: DDD-based domains, device API abstraction for consoles/TVs, independent bundles a few KB each. Outcome: supports millions of users and teams growing from 3 to 200–300, reduces cross-team coordination and speeds experimentation.
AI-written summary · about
chapters (8)
- 0:00Start
- 14:11IMPACT WITH THE TEAMS
- 17:56LEARN FROM OTHERS
- 21:48DAZN MICROFRONTENDS MANIFESTO
- 24:53WHAT IS ACTUALLY A MICROFRONTEND?
- 26:33WHAT IS BOOTSTRAP?
- 26:58LOADING FLOW
- 27:55BOOTSTRAP RESPONSIBILITIES & BENEFITS
related talks
37mDemystifying Micro-Frontends
27mMicro Frontends: Break Up You Web App!
24mScaling Frontend Development using Micro-frontends
36mMicro Frontends - Breaking Monoliths
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
29mMicro Frontends, how to evolve to an extensible frontend
10mMicrofrontends done right
33mMicro Frontend Architecture