From REST to GraphQL
summary
Argues GraphQL replaces many REST endpoints with one endpoint that returns exactly the requested shape, cutting multi‑round‑trip fetches (example: painful seven round trips) while avoiding overfetch. Shows concrete tooling and techniques: GraphiQL for introspection, GraphQL batch loaders to eliminate N+1 queries, and normalized client cache (Relay/Apollo) to keep single-source state. Demonstrations claim batching and caching work in practice but require careful setup, query depth/timeouts and complexity limits to stay safe.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:41About me
- 1:08UI component
- 2:07REST
- 3:19Query params
- 4:22Custom endpoints
- 6:00What is GraphQL
- 6:51GraphQL field query
- 7:39Query route
- 9:07Query type
- 10:04Query fragments
- 11:46Query children
- 13:24GraphQL Documentation
- 13:52Resolving Fields
- 15:06Query Response
- 15:31Mutations
- 15:57Drawbacks
- 16:36Nested queries
- 17:07Loaders
- 17:51HTTP Cache
- 20:13GraphQL is just a layer
- 20:45Defending against malicious queries
- 21:55GraphQL Subscriptions
- 22:24GraphQL Queries
- 23:04Conclusion
