Reactive State Management For Your Angular App
summary
Explains how a centralized ngrx/store plus RxJS replaces prop drilling in an Angular app by converting component communication into dispatched actions, reducers and selectors; demo is a working tweet-search app with add-message and slider UI that uses Effects to handle async HTTP/WebSocket work and splits each async flow into three actions (start/success/failure). Shows selectors with memoization, Redux DevTools and a development freeze module, claims measurable simplification of reasoning and rendering but warns of notable boilerplate and architectural discipline.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:49Maxim Salnikov
- 3:49Increasing complexity
- 4:49Unidirectional
- 5:41State complexity
- 8:18Redux is simple
- 12:35Main principles
- 14:24Immutability?
- 18:35Demo app
- 20:48State Management Container
- 22:50Action with payload
- 23:19Reducer
- 24:23Wiring up all together
- 24:58Injecting the store
- 25:45Creating selectors
- 26:50Async action
- 28:25Creating effect
- 30:00Actions for effects
- 30:40Running effect
- 31:14Redux DevTools
- 32:07Out of today's scope
- 33:02To sum up
related talks
44mAngular + Redux ... stop, what?
01h 04mRedux for Angular -- Introduction to Ngrx Ecosystem
39mFrom Inactive to Reactive with ngrx
52mState Management in Angular: From Facades to NgRx and back
30mState Management Patterns and Best Practices with NgRx
20mState Management at Scale w/NgRx
27mngRx the last piece in the Angular architecture puzzle
54mReactive Angular 2