Scalable Angular Architecture
summary
Argues that scalable front-end applications need concrete structure not buzzwords and lays out a reproducible stack: separate presentation, facade and core layers so components never touch the global store directly; use RxJS streams and ngrx store style uni‑directional flow; implement lazy loading and modular routes to cut initial bundle size; prefer facade-level pessimistic updates for server consistency; split smart and dumb components so features can be built, tested and onboarded with minimal cross‑module coupling.
AI-written summary · about
chapters (11)
- 0:00Start
- 4:38Problems of scalability in front-end
- 16:43Abstraction layers
- 16:53Presentation layer
- 20:40Core layer
- 21:16Unidirectional data flow
- 26:56Predictable state management
- 28:25Smart & Dumb Components
- 30:23Modularization - directory structure
- 32:19Lazy loading
- 32:32Preloading
related talks
26mScalable Angular Architecture
22mHow to make robust and scalable front-end using layers
27mAngular Architecture: From Patterns to Implementation
22mScalable Angular Application Architecture
25mAngular Architecture: From Patterns to Implementation
30mAngular: Keeping it Fat, Dumb, and Happy: An Architectural Approach
31mArchitectures for huge Angular based enterprise applications npm Packages, Monorepos and Micro Apps
17mRethinking Angular Architecture & Performance