Scaling Frontend Development using Micro-frontends
summary
Explains concrete ways to split a large SPA into independently deployable pieces and reports what actually works and fails: use simple hyperlinks or iframes for isolation, adopt single-spa to mount multiple frameworks in one DOM, or compile to web components; mitigate bundle bloat with SystemJS dynamic loading or server-side chunking; sync state via localStorage, backend persistence or events; preserve UX with a central design guild; require independent unit tests plus end-to-end integration; overall verdict: useful but adds nontrivial tooling and operational overhead.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 1:57Why micro-frontends
- 8:17What are micro-frontends
- 16:09Overheads and challenges
- 21:52Testing and best practices
- 22:56Final recommendations
related talks
27mMicro Frontends: Break Up You Web App!
48mMicrofrontend Architecture – technical implementation.
57mMicro Frontends – a strive for fully verticalized systems
36mMicro Frontends - Breaking Monoliths
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
32mYou don't know Microfrontends
47mCamel and Eye of a Needle: Integration Approaches for SPA-based Micro Frontends
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
