State management in a GraphQL era
summary
Claim: with GraphQL (Apollo) the data problem largely disappears and in about 90% of cases Redux is unnecessary. Demonstrations compare a verbose Redux fetch flow, a compact MobX observable class, and an Apollo query attached to a ToDo component that gives automatic caching and loading state. Argument stresses choosing tools for the app and team, notes GraphQL can coexist with other state libraries, and warns using Redux alongside Apollo often amounts to over‑engineering.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:38REST vs GraphQL
- 1:13State management
- 1:29Data
- 1:59Whats better
- 2:25Simple todo lists
- 3:00Fixing the sink
- 3:16Recap
- 3:43Conclusion
related talks
24mReact State Management In a GraphQL Era
27mReact State Management In a GraphQL Era
52mState management in a GraphQL era
25mReact state management in a GraphQL era
30mReact state management in a GraphQL era
22mReact State Management in a GraphQL Era
24mState Management in React Apps with Apollo Client
27mLet’s manage our local state with GraphQL