To Micro Frontend or Not to Micro Frontend
summary
Five concrete questions determine whether to adopt micro frontends: which integration method (build time vs runtime), whether to use Module Federation or import maps, how apps will communicate (custom event bus vs pub/sub), how to enforce a single design system and avoid CSS/dependency duplication, and whether the architecture actually solves the team problem. Examples include Capital One and Ikea, a case with 3 separate React apps in one repo, Go back ends, and tradeoffs around duplicated bundles and deployment independence.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:52Micro frontend architecture
- 5:18Pros and cons
- 8:30Integrating micro frontends
- 13:24Module Federation
- 17:18Communication between apps
- 19:45Consistency across apps
- 24:19Key adoption questions
- 25:02Conclusion & Q&A
related talks
52mMicro frontends: prepare for the ride
57mMicro Frontends – a strive for fully verticalized systems
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
30mWhen to Use Microfrontends? (and When to Avoid Them!)
14mMicro-frontends: Is it a Silver Bullet?
45mMicro Frontends in Action!
20mBuilding Microfrontends on AWS
29mMicro Frontends, how to evolve to an extensible frontend