Micro Frontends: Break Up You Web App!
summary
Claims that splitting work by use case gives teams end-to-end ownership and cuts coordination overhead, tested on real e‑commerce projects with 10–60 developers per client. Implementation uses custom elements (web components) plus server-side includes for initial HTML, treats the DOM as the team-to-team API, and relies on HTTP/2, lazy loading and progressive enhancement. It ships independent fragments and a thin page shell successfully in production while warning against shared runtimes and urging prefixed CSS and optional pattern libraries.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:41Architecture
- 7:11Technical Teams
- 9:40Team Checkout
- 11:44How to integrate?
- 12:18Web Components
- 20:34Page Transitions
- 22:38Things we've learned
- 23:31Isolate Teams don't share runtime, state or globals
- 23:57Talk to your Neighbors share best practices
- 25:24Ownership is important use team prefixes when needed
- 26:04Have a Design System
related talks
25mMicrofrontends: a Modern Approach to Complex Web Applications
57mMicro Frontends – a strive for fully verticalized systems
37mDemystifying Micro-Frontends
36mMicro Frontends - Breaking Monoliths
29mMicro Frontends, how to evolve to an extensible frontend
24mScaling Frontend Development using Micro-frontends
29mMicro Frontends, or How to Evolve to an Extensible Frontend
45mMicro Frontends in Action!