React Query: It’s Time to Break up with your "Global State"!
summary
Argument: most “global state” is actually server data and deserves different tooling. Demonstration builds a small interactive blog, swaps custom hooks + context for React Query, removes about 150 lines of code, and gains caching, background refetching, per-key queries, and declarative mutation handling. Mutations use optimistic updates with rollback (demo has a 50/50 simulated failure). Result: fewer bugs, instant cached views, and simpler code for async server state.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:45Global State vs Server State
- 6:47Project Overview
- 12:44Post ID Search
- 16:10React Query
- 21:45Conclusion
- 23:43Audience Questions
related talks
25mReact Query Under the Hood
11mSimple data fetching with React Query
41mReact Query: The Next Big Library?
30mReact state management in a GraphQL era
27mLet's Build React Query in 150 Lines of Code!
20mReact Query API Design – Lessons Learned
27mReact State Management In a GraphQL Era
25mReact state management in a GraphQL era