Complexity Management with NgRx
summary
An early AngularJS project sits unupdated for five years because tangled services, controllers and promise-based race bugs make maintenance impossible. The claim: NgRx replaces that mess with reducers and actions (pure state transitions), isolates behavior into effects with actions$ and ofType that call services via RxJS and map results back to actions, and accepts higher code cost. NgRx 8 reduces that cost with createAction/createReducer. Effects use RxJS cancellation operators to avoid race conditions and make control flow testable.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 3:00What is NgRx
- 5:28Managing state in NgRx
- 10:29Code volume in NgRx
- 13:18Control flow with effects
- 17:32Summary and takeaways
related talks
20mState Management at Scale w/NgRx
29mReducing Complexity with Ngrx
52mState Management in Angular: From Facades to NgRx and back
01h 04mRedux for Angular -- Introduction to Ngrx Ecosystem
26mState Management Patterns and Best Practices with NgRx
27mWhy You Should Definitely Use NgRx
30mState Management Patterns and Best Practices with NgRx
35mAdvanced NgRx Techniques
