State Management Patterns and Best Practices with NgRx
summary
NgRx is presented as the default Angular state library for large apps and the talk documents concrete patterns: actions split into commands documents events, effects that act as filters/deciders/transformers (splitter, aggregator), reducers as pure state updaters, and using correlation IDs for request/reply. Example: add‑todo dispatches a command, an effect posts to backend, then dispatches a persisted event that a reducer applies; composition of these primitives solves complex workflows without exploding class count.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:30Who is Victor?
- 0:52Shameless Plugs
- 1:14What we'll cover
- 2:40Create and Dispatch
- 3:10Receive and Process
- 5:16React to State Changes
- 8:04Categories of Actions
- 8:58Documents
- 9:41Commands and Events
- 12:54Correlation ID
- 15:04Filtering Decider
- 15:28Content-Based Decider
- 16:42Splitter
- 17:04Aggregator
- 19:17Content Enricher
- 20:54Composing Building Blocks
- 22:08Normalizer & Canonical Actions
- 25:35Summary
related talks
30mState Management Patterns and Best Practices with NgRx
20mState Management at Scale w/NgRx
52mState Management in Angular: From Facades to NgRx and back
29mReducing Complexity with Ngrx
20mComplexity Management with NgRx
01h 04mRedux for Angular -- Introduction to Ngrx Ecosystem
27mWhy You Should Definitely Use NgRx
35mAdvanced NgRx Techniques