Breaking the Monolith: A Comprehensive Guide to Code Splitting
recording made private on YouTubehttps://youtu.be/kiL0mpjHiXE
summary
Six concrete ways to split a monolith with tradeoffs and triggers: iframe embeds for simple modules, proxy (nginx) for framework migrations at the cost of performance, web components for a cross‑platform UI kit, npm packages as an easy first step but with harder debugging and release flow, single-spa for per‑URL apps and lifecycle control, and webpack 5 module federation to share modules and cache libraries so React isn’t loaded N times. Triggers to break are long CI (eg 6 hour builds), rising complexity, onboarding limited to seniors, or more than five active developers.
AI-written summary · about
related talks
32mFrom Monolith to Micro Frontend
24mScaling Frontend Development using Micro-frontends
41mMicro-frontends: the golden circle
25mBreak up Monoliths and lay them to REST!
22mBreak Up With Your Frontend Monolith
15mBreaking Down Monoliths: Microfrontend Architecture with React
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
36mMicro Frontends - Breaking Monoliths