Architecting complex JavaScript setups for large scale enterprise projects
summary
Claims that microfrontends scale only if teams map to business domains and own independent release cycles, demonstrated with a live host + remote composition using module federation (webpack 5) and an Angular element built as a standalone web component. Integration techniques compared: iframes for strong encapsulation, single-spa for routing/composition, and ES imports/web components for sharing. Demo shows an iframe communicating via event bus via window.postMessage and a federated remote loaded by remote_entry.js (~3KB loader); webpack enforces shared deps and version checks, and serverless/static builds affect performance (LCP, FID, CLS).
AI-written summary · about
chapters (11)
- 0:00Start
- 13:03Modularization Era
- 21:19Modular Monolith
- 31:18Container Types
- 36:44Mono Repositories Pattern
- 39:42Css Abstracts
- 42:50State Management
- 49:37Cumulative Layout Shift
- 51:33Static Site Generators
- 54:47Module Federation
- 56:19Shared Dependencies
related talks
31mMicro frontends and the multiverse of Frameworks
45mMicro Frontends in Action!
48mMicrofrontend Architecture – technical implementation.
36mMicro Frontends in Action!
24mScaling Frontend Development using Micro-frontends
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
01h 17mChallenges in Building Micro Front Ends
25mAdvanced Micro Frontends: Multi-Version and Multi-Framework Scenarios
