Make React State-Management great again
summary
Compares concrete implementations and tradeoffs: the team chooses Redux with normalized store and shows how normalizing three API shapes into one entity reduces duplication and bugs, wires sagas for user-stories to express onboarding flows as readable sequences, and measures perf fixes by replacing cheap filters with reselect memoized selectors to avoid needless renders; shows middleware and logging benefits, how state shape and selector choices actually change render counts, and what setup steps make a large app maintainable.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:52Location
- 8:06Mutability
- 9:43Community
- 10:43Performance
- 11:41Logging
- 24:34What happens when you fire an action?
- 26:44Memoized selectors
related talks
41mThe Battle of State Management in modern frontend applications
18mDestructuring state management (in React)
28mThe State of React State in 2019
51mBuilding React Applications with Redux
15mRedux is dead, long live redux!
45mRedux and Redux-saga to manage states in a large React app
29mStructure Your App's Story With Sagas and Selectors
29mAvoiding the Biggest Mistakes in React State Management