State Management Patterns and Best Practices with NgRx
summary
Explains concrete NgRx patterns: actions split into commands documents events, request–reply via correlation ID stored on entities, and effects as the place for side effects and coordination using RxJS operators (filter, splitter, aggregator, content enricher). Shows examples (to‑do add/delete, confirmation dialog) and a recipe for composing deciders and transformers so reducers stay pure. Treats the store as a client‑side database and recommends Enterprise Integration Patterns and Nx for scaling large Angular apps.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:39Overview
- 1:31Enterprise Integration Patterns
- 2:13Lifecycle of an Action
- 4:30Actions
- 7:31Dispatching an Event
- 11:29Correlation Ids
- 11:42Correlation Engine
- 14:19Filtering Decider
- 14:38Quantum Bass Decider
- 16:37Splitter
- 17:07Aggregator
- 18:44Transforming Actions as Actions
- 19:36Normalizing Canonical Action
- 22:55Recap
related talks
26mState Management Patterns and Best Practices with NgRx
52mState Management in Angular: From Facades to NgRx and back
35mAdvanced NgRx Techniques
20mState Management at Scale w/NgRx
32mMessaging Design Patterns with NGRX
27mWhy You Should Definitely Use NgRx
34mReactive State Management For Your Angular App
27mAngular Architecture: From Patterns to Implementation