Microfrontends: Scalability Savior or Unmanageable Maze?
summary
Claims microfrontends solve organizational scaling not technical problems and shows concrete evidence: a demo with three microfrontends demo that rebuilds one part independently, production experience across six systems at a 200,000-employee telecom, and seven projects consulted. Tools used include single-spa and Webpack Module Federation and patterns like iframes and web components. Works well for portal-like apps and field‑service UIs; fails as an “enterprise app store” due to shared design system collisions, web component registration issues, multi‑framework payload bloat, and heavy DevOps governance needs.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:29Traditional frontend scaling
- 3:58Scaling frontend challenges
- 5:21What are microfrontends
- 8:52Microfrontend tools
- 10:21Why microfrontends trend
- 12:31Microfrontends in practice
- 14:59Team independence
- 16:27Independent deployments
- 18:39Reusing microfrontends
- 21:09Framework agnosticism trade-offs
- 22:55Maintaining microfrontend tools
- 24:21Technical scalability
- 24:42Organizational scalability
- 27:11When microfrontends work
- 29:21Common pitfalls
- 30:44Microfrontends as tool
- 31:07Q&A
related talks
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
52mMicro frontends: prepare for the ride
10mMicrofrontends done right
57mMicro Frontends – a strive for fully verticalized systems
37mDemystifying Micro-Frontends
14mMicro-frontends: Is it a Silver Bullet?
34mMicro Frontends
45mThe Problems Micro Frontends Won't Solve That No One Wants to Talk About