Micro Frontends - Breaking Monoliths
summary
Claim: micro frontends let each UI fragment live in independent repos and deploy separately so versions change without redeploying the whole app. Architecture uses an appshell that registers routes and containers and a plugin manager that pulls fragment JS at runtime (demo uses three modules on ports 8081/8082). Recommended tooling includes single-spa or a custom loader; must solve domain boundaries, a shared design system, data exchange via backend/pub‑sub, centralized router, CI/CD, and SSO with a cookie token.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:47Monolith to Microservices
- 5:07What are Micro Frontends
- 7:20Why adopt Micro Frontends
- 12:23Key challenges in Micro Frontends
- 22:22Frameworks for Micro Frontends
- 25:51Live Micro Frontend demo
- 30:39Q&A session
related talks
57mMicro Frontends – a strive for fully verticalized systems
36mMicro Frontends in Action!
48mMicrofrontend Architecture – technical implementation.
33mMicro Frontend Architecture
19mHarnessing Microfrontends: Platforms for Web Apps
27mMicro Frontends: Break Up You Web App!
45mMicro Frontends in Action!
29mMicro Frontends, how to evolve to an extensible frontend
