Micro Frontends, or How to Evolve to an Extensible Frontend
summary
Argues for splitting a web frontend into independent microfrontends mapped to business subdomains and demonstrates using iframes to compose a todo app into editor, list, and rack components. Shows that an individual iframe can be redeployed to fix a CSS bug (enabling fragment releases) and discusses tradeoffs such as version skew between microfrontends, larger payloads, and the need for integration tests despite improved deployment granularity and easier team onboarding.
AI-written summary · about
chapters (9)
- 0:00Micro frontends intro
- 3:58Frontend evolution
- 8:53Definition
- 10:17No frameworks
- 11:46Demo with iframes
- 17:28Deploying components
- 21:45Project flexibility
- 23:31Pros and cons
- 26:41When to use
related talks
34mMicro Frontends
27mMicro Frontends: Break Up You Web App!
57mMicro Frontends – a strive for fully verticalized systems
45mMicro Frontends in Action!
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
37mDemystifying Micro-Frontends
10mMicrofrontends done right
36mMicro Frontends - Breaking Monoliths