React State Management In a GraphQL Era
summary
Argues that GraphQL plus a client like Apollo removes most data-state pain — fetching, caching and invalidation — and that teams often drop 5,000 lines removed when replacing Redux data plumbing with GraphQL. Shows stacks: Apollo alone with setState, Redux for global logic, MobX for local reactivity, Next.js for SSR, and client tricks like refresh queries on mutation instead of complex cache updates. Demonstrates Apollo tools such as Apollo link state and cache persistence and reports these simpler approaches working well for fast-changing MVPs.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:45React Amsterdam 2016
- 1:23Rockstar developer
- 8:09Explaining Redux to someone
- 10:52Examples
- 16:41A client project story
- 19:33Router example(s)
- 22:00Service worker example
related talks
27mReact State Management In a GraphQL Era
22mReact State Management in a GraphQL Era
25mReact state management in a GraphQL era
30mReact state management in a GraphQL era
05mState management in a GraphQL era
52mState management in a GraphQL era
27mLet’s manage our local state with GraphQL
24mState Management in React Apps with Apollo Client