Angular Architecture: From Patterns to Implementation
summary
Argues that concrete design patterns—modules, container vs presentational components, and a one‑way Redux style state tree—produce predictable, testable Angular apps. Demonstrates using ngrx store with actions, reducers, selectors and the ngrx/entity helper, binds router state into the store, and recommends OnPush change detection and async pipes to keep presentational components stateless. Shows the restaurant analogy mapping to actual implementation details and claims this scales and isolates bugs when applied.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:29From Patterns to Implementation
- 2:50Why Are Systems Important
- 9:04Stock Management
- 12:15Application Architecture
- 14:18Redux Pattern
- 16:04Container Component
- 17:09Stateless Child Components
- 17:50Modules
- 18:57Reducers
- 19:25Selectors
- 19:39Roots of State
- 20:14Component Architecture
- 23:33State Management
- 25:51Abstract Your Logic
related talks
25mAngular Architecture: From Patterns to Implementation
26mScalable Angular Architecture
34mScalable Angular Architecture
30mState Management Patterns and Best Practices with NgRx
24mDay 2 Keynote, Angular Architecture Concepts and Practices
32mMessaging Design Patterns with NGRX
24mThe Architecture of Components
01h 04mRedux for Angular -- Introduction to Ngrx Ecosystem