From Monolith to Micro Frontend

on YouTube ↗32m

" summary

Maps three concrete migration patterns and the tradeoffs observed: keep the monolith and mount independent SPAs (fast to start but causes style conflicts and poor shared-module performance), introduce a shell application that reads a catalog JSON and composes microfrontends (enables independent deployment and preserves auth but adds an orchestration layer), or route at the edge with Lambda Edge for full offload (higher cost and token/header work). Recommends Webpack Module Federation or single-spa, web components, NX, CI/CD automation, and phased rollout — migration succeeds with careful boundaries and tooling.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 3:14Monolith challenges
3. 10:03Micro frontends overview
4. 11:51Strategy one: Independent SPAs
5. 14:08Strategy two: Shell application
6. 17:43Strategy three: Routing on edge
7. 20:34Migration tips
8. 29:12Conclusion and resources

" related talks

• 48mMicrofrontend Architecture – technical implementation.Reinis Pakers · DevClub.lv 114th Frontend focused event
• 24mScaling Frontend Development using Micro-frontendsMashhood Rastgar · NG-MY 2019
• 36mMicro Frontends - Breaking MonolithsBipul Kumar · Developer Summit 2020
• 25mMicro Frontend: a microservice architecture from your frontend web appsWilson Mendes · JSConf.Asia 2018
• 11mTransforming Enterprise Frontends with Micro-Frontend ArchitecturesNasir Sayed · Site Reliability Engineering (SRE) 2025
• 57mMicro Frontends – a strive for fully verticalized systemsDavid Leitner · NDC London 2020
• 24mMicrofrontendsDavid den Toom · React Live 2019
• 31mMigrating from Monolith to MicrofrontendsYaprak Ayazoglu · ConfrontJS 2018