GraphQL Will Do To REST What JSON Did To XML
summary
Argues GraphQL replaces REST by exposing a single endpoint that returns flexible shapes so a marketplace UI (product + reviews + paginated offers) stops suffering N+1 and over/under‑fetching; shows an Apollo Server implementation with type defs, resolvers, context and dataSources wiring to databases and third‑party APIs and demos the Apollo Playground querying only requested fields; cites ecosystem scale — over a million weekly downloads and ~20,000 GitHub projects — and demonstrates the approach working and reducing client/server complexity.
AI-written summary · about
chapters (11)
- 0:00GraphQL vs REST intro
- 2:08REST problems and over-fetching
- 9:52GraphQL solves REST limits
- 10:34GraphQL schema and queries
- 16:59Over-fetching and pagination solved
- 18:03GraphQL versioning and deprecation
- 19:28GraphQL playground and docs
- 21:33Backend and DB implementation
- 26:50GraphQL tooling and adoption
- 29:58Why GraphQL for APIs
- 32:29Q&A
related talks
36mGraphQL Will Do To REST What JSON Did To XML
18mGraphQL Will Do To REST What JSON Did To XML
37mGraphQL — A New Look at the API
46mGraphQL 101 - Stop RESTing, Start Querying
29mFrom REST to GraphQL
01h 02mGoodbye REST APIs. Hello GraphQL!
33mGraphQL - the What, how and why
54mGraphQL — Usable API or Just Another Hype?