The Perfect Micro Frontends Platform
summary
Argues that microfrontends succeed only when organization, culture and architecture align; recommends Module Federation for loading shared bundles, a tiny container-facing API per MFE, reassessing boundaries every six months, and minimizing shared libraries in favor of controlled duplication. Describes edX’s migration to Piral, a JSON-schema driven discovery + canary/blue-green rollout flow, and an open-source frontend service discovery component used in production. Insists each MFE team must code test deploy and monitor its MFE and enforce CI fitness checks for bundle size and performance.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:01Micro-frontend motivations
- 4:04Case study: edX journey
- 8:24Defining micro-frontends
- 16:04Organizational alignment
- 21:53Platform team responsibilities
- 29:00Developer experience
- 33:19Deployment and discovery
- 37:31Value stream best practices
- 43:57Closing and Q&A
related talks
44mMicro Frontend Discovery
52mMicro frontends: prepare for the ride
27mMicro-frontends: anti-patterns
35mMicro-Frontend & Me, a love story
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
29mMicro Frontends, how to evolve to an extensible frontend
38mFrom Microfrontends and back
22mMicro Frontends & me, a love story