Avoiding the Biggest Mistakes in React State Management
summary
Covers concrete failures and fixes: a component with 27 props that breaks reuse, monolithic global stores that force rewrites and cause $50,000 outages, and a system that handles a few thousand users but collapses at 50–70k users. Shows the actual fixes used — component composition and Context API to stop prop drilling, decentralized domain stores plus selectors to avoid bloat, and network‑aware libraries (TanStack, SWR, Apollo) to cache and unify server state so pages load reliably.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:15State management confidence
- 3:39State management in React
- 5:05Local state pain points
- 8:40Fixing prop drilling
- 11:05Global state bloat
- 13:35Focused stores solution
- 15:45Server state mistakes
- 17:09Manual server state symptoms
- 19:17Network-aware tools
- 20:45State confidence framework
- 22:11State decision questions
- 26:04Choosing state tools
- 28:11Recap and takeaways
related talks
30mMake React State-Management great again
20mAvoiding Expensive Mishaps with Effective State Management
55mThe State of React’s State in 2019
28mThe State of React State in 2019
17mManaging React State: 10 Years of Lessons Learned
01h 00mEffective React: Lessons from 10 Years
40mManaging Complex State in React
30mManaging State Management