React state management in a GraphQL era
summary
Claims that GraphQL pushes most server data problems to the client and makes global state libraries unnecessary in many cases, with concrete stacks: Apollo + setState for simple apps, MobX + minimal glue for quick wins, Next/SSR + per-page mini-apps for separating concerns. Examples: a 4,000-line jQuery calendar, a tiny randomizer app built to test caches, production migration removing 5000 lines removed, 1000 added when moving off Redux, clients (IKEA, Deutsche Telekom) running Apollo without manual cache hacks, and a service-worker domain bug.
AI-written summary · about
chapters (5)
- 0:00Start
- 11:22Examples about Data Fetching
- 13:52Example Stacks
- 14:32High Heat Forms
- 28:43Stop Seeking External Approval
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
27mReact State Management In a GraphQL Era
05mState management in a GraphQL era
36mThe State Management Rollercoaster
24mState Management in React Apps with Apollo Client