Micro-frontends: the golden circle
summary
Company case study of breaking a Rails monolith with ~15 frontend engineers into independently deployable pieces for smaller bundles and faster change cycles, using webpack optimizations and code splitting but moving orchestration complexity to composition, CI and testing. Explored server-side composition, edge includes, iframes and a client-side orchestrator and libraries like single-spa and Frint.js; reports gains in independent deployments, ownership and incremental upgrades but warns about SEO, duplicate libraries, design fragmentation and heavier deployment automation.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:09What are micro-frontends
- 6:10Why use micro-frontends
- 9:29Scaling with micro-frontends
- 10:57Advantages of micro-frontends
- 15:16Challenges of micro-frontends
- 19:30Implementing micro-frontends
- 26:12Trade-offs in micro-frontends
- 28:18Tips for micro-frontends
- 32:30Formal definitions
- 35:44Summary and wrap-up
- 39:26Q&A and closing
