Micro frontend Has Entered the Game
summary
GitLab describes running micro frontends at scale: 60+ frontend engineers maintain ~500k lines of JavaScript across 20+ micro-apps inside ~40 product apps with a CI pipeline ~1 hour long. The payoff is independent deployment and faster experiments, but they found duplicated code (122 large blocks), many duplicate test utils (171 utils.jest files), competing state solutions, and cross-team dependencies; the approach requires business buy-in, strong DevOps, feature flags and a slow incremental migration to avoid maintenance and coordination debt.
AI-written summary · about
chapters (13)
- 0:00Welcome
- 1:27What is micro frontend
- 3:34Domain-driven design
- 4:15Micro frontend myths
- 6:47GitLab implementation
- 7:53Micro frontend advantages
- 12:06Micro frontend pitfalls
- 15:33Code duplication
- 19:53Avoiding technical debt
- 21:20Key success conditions
- 24:48DevOps and culture
- 26:33Summary
- 26:57Q&A
related talks
37mDemystifying Micro-Frontends
29mMicro Frontends, how to evolve to an extensible frontend
21mMicro-frontends: 3 years ago
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
22mMicro Frontends & me, a love story
24mMicrofrontends
10mMicrofrontends done right
14mMicro-frontends: Is it a Silver Bullet?