Micro Frontends, how to evolve to an extensible frontend
summary
Claims that micro frontends let teams ship and fix small parts independently, demonstrated with a tiny todo app split into editor, list and a shell, wired via iframes and a simple messaging API. A deploy script publishes only the list micro-app, reproducing a hover-color bug fix without touching the rest. Notes tradeoffs: higher integration-test burden, larger duplicated bundles and version coordination. Recommends use for diverse business domains or when fragmented releases are likely, not for trivial single-page apps.
AI-written summary · about
chapters (10)
- 0:00Micro frontends evolution
- 3:57Monoliths to micro frontends
- 7:13Facebook’s pagelet approach
- 10:11Demo setup and architecture
- 16:48Wiring micro frontends
- 18:08Deploying bug fixes
- 21:47Key lessons and flexibility
- 23:33Pros and cons
- 26:40When to use micro frontends
- 29:06Q&A
related talks
34mMicro Frontends
27mMicro Frontends: Break Up You Web App!
57mMicro Frontends – a strive for fully verticalized systems
33mMicro Frontend Architecture
37mDemystifying Micro-Frontends
36mMicro Frontends - Breaking Monoliths
10mMicrofrontends done right
25mMicrofrontends: a Modern Approach to Complex Web Applications