State management in a GraphQL era
summary
Single-page apps push complexity to the client so the real state problems are fetching caching reading invalidation, not UI wiring. Concrete fixes shown: hand-rolled caches fail at normalization, Redux adds boilerplate, MobX simplifies local cases, and GraphQL with Apollo moves data logic back to the client library — one refactor replaces ~5,000 lines of Redux code with ~1,000 lines using Apollo. demos include a face‑randomizer (worked) and using Apollo cache-persist for offline; pragmatic tip: refetch queries after mutations to save engineering time on fast‑changing MVPs.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:09Caching Mechanism
- 15:46Pull Request
- 23:41Context Api
- 25:07Header
- 28:32Add Provider
- 32:25Basket Actions
- 37:40Export Cost Initial State
- 50:52Summary
related talks
30mReact state management in a GraphQL era
27mReact State Management In a GraphQL Era
24mReact State Management In a GraphQL Era
25mReact state management in a GraphQL era
05mState 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