Architecting large scale Angular apps with Module Federation
summary
Claims that splitting an Angular monorepo into buildable libraries plus vertical app slices cuts local serve and CI times dramatically, using Webpack Module Federation to load compiled remotes and NX to generate and wire remotes. Concrete tooling: Module Federation, NX generators and its affected-graph caching, and NX Cloud shared cache. Demonstrated numbers: multi-minute cold builds versus cached incremental runs dropping to seconds (example: ~1+ minute cold to ~7s cached), with incremental migration commands and static-served remotes.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:38Scaling challenges in software
- 4:09Organizing large workspaces
- 8:09Enforcing code boundaries
- 10:35Optimizing build performance
- 13:25Incremental builds and caching
- 17:11Vertical slicing with MF
- 20:07Module federation in action
- 26:57Nx cloud and sustainability
- 29:02Conclusion and resources
- 33:30Q&A session
related talks
30mFederated Angular: Micro Frontends with Module Federation
21mAngular based Micro frontends with module federation
30mFederated Angular: Micro Frontends with Module Federation
41mThe Microfrontend Revolution
38mThe Microfrontend Revolution: Using Webpack 5 Module Federation with Angular
22mFederated Angular - Why and How
31mMicro frontends and the multiverse of Frameworks
22mRoad to Module Federation
