React State Management In a GraphQL Era
summary
Argues that moving data fetching to GraphQL simplifies client state: switching from Redux to GraphQL+Apollo removes about 5,000 lines of Redux boilerplate in one pull request, and common cases use simple component queries rather than manual normalization. Shows practical tradeoffs: use cache persist to support offline instead of a full Redux stack, and prefer occasional refetch-all calls over brittle Apollo cache invalidation for small apps. Recommends treating pages as mini-apps to avoid global state, and warns against overengineering single-page apps.
AI-written summary · about
chapters (9)
- 0:00The myth of developer labels
- 3:22Defining developer roles
- 6:06Single page apps and data
- 8:21Reflecting on state frameworks
- 10:48Finding simpler alternatives
- 13:21GraphQL as a data solution
- 16:04Practical stack selection
- 18:50Avoiding over-engineering
- 22:14Conclusion and final advice
related talks
24mReact State Management In a GraphQL Era
25mReact state management in a GraphQL era
52mState management in a GraphQL era
22mReact State Management in a GraphQL Era
30mReact state management in a GraphQL era
05mState management in a GraphQL era
27mLet’s manage our local state with GraphQL
24mState Management in React Apps with Apollo Client