Angular + Redux ... stop, what?
summary
Shows how ngrx (Redux for Angular) provides a single store for application state and how @ngrx/effects handles asynchronous flows using a small e‑commerce demo: clicking a book dispatches actions, reducers update one store, selectors compute cart and recommendations, and router state plus a canActivate guard load data before navigation. Mentions testing complexity for branching effects (recommends marble tests) and lists package sizes (~5 KB for core, ~2.5 KB for effects).
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:18Angular data storage issues
- 7:53Redux in Angular
- 13:54Selectors for state
- 18:06Scaling with Redux
- 21:47Testing Redux effects
- 23:28Redux scaling solutions
- 24:57Complex state management
- 27:25Component testing with selectors
- 30:42Actions sync vs async
- 32:05Business logic in Redux
- 34:30State immutability
- 37:18Redux for real-time apps
- 41:16Effect execution order
- 42:27Redux vs alternatives
- 44:13When to use Redux in Angular
related talks
01h 04mRedux for Angular -- Introduction to Ngrx Ecosystem
34mReactive State Management For Your Angular App
27mngRx the last piece in the Angular architecture puzzle
29mRedux Data Flow with Angular 2
27mWhy You Should Definitely Use NgRx
35mAngular and Redux in practice
35mAdvanced NgRx Techniques
52mState Management in Angular: From Facades to NgRx and back