State Management at Scale w/NgRx
summary
An AngularJS→Angular migration with NgRx serves as a concrete case study: a Fortune 500 app with 300 developers uses NgRx, NX monorepo, selectors, effects and actions to untangle service spaghetti, replace in-place mutations and remove AngularJS connections. The project ships generators, standardizes createFeature and shared action libraries, and later retrofits component store patterns; results are measurable: migration completes, team velocity improves, test surface grows and no more shared mutated state causes fewer production surprises.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:43Backstory
- 3:28State Management
- 5:22Angularjs Store
- 8:52Action Hygiene
- 11:03Sherry Principle
- 13:05Patterns Practices
- 17:29Lessons Learned
related talks
27mWhy You Should Definitely Use NgRx
20mComplexity Management with NgRx
26mState Management Patterns and Best Practices with NgRx
30mState Management Patterns and Best Practices with NgRx
52mState Management in Angular: From Facades to NgRx and back
34mReactive State Management For Your Angular App
28mProgressive State Management: NGXS
01h 04mRedux for Angular -- Introduction to Ngrx Ecosystem