React State Management in a GraphQL Era
summary
Compares concrete stacks: GraphQL with Apollo replacing most data plumbing, Redux or MobX only for specific needs, and Next.js for easy SSR; claims a team cuts ~5,000 lines removed after moving to Apollo. Demonstrates Apollo 2.0 with pluggable links and a new in‑memory cache that is 10x faster, shows offline queries work with redux‑offline but offline mutations require wrapping mutations as Redux actions, and previews Apollo link‑local for client state via a client schema.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:20What is GraphQL
- 2:30Why State Management is Hard
- 3:23Angular State Management
- 4:15Why Redux
- 5:41Example Post
- 7:36Whats Better
- 10:44Vanilla
- 11:37Redux Offline
- 15:30Serverside Rendering
related talks
24mReact State Management In a GraphQL Era
25mReact state management in a GraphQL era
30mReact state management in a GraphQL era
27mReact State Management In a GraphQL Era
52mState management in a GraphQL era
05mState management in a GraphQL era
24mState Management in React Apps with Apollo Client
23mGraphQL State Management for React Native