GraphQL — A New Look at the API
summary
GraphQL is presented as a replacement for many REST endpoints by letting clients declaratively request exact fields from a typed schema, reducing dozens of requests (examples given: 25 requests, 10–15–20). The server works as an API gateway that aggregates multiple microservices, with tooling like GraphiQL, Apollo and graphql-js; queries execute in parallel while mutations run sequentially, cursor-based pagination replaces unstable offsets, and features such as fragments, interfaces, unions and custom directives enable reuse and control; several teams report production deployments and tradeoffs.
AI-written summary · about
chapters (10)
- 0:00GraphQL introduction
- 3:11GraphQL vs REST problems
- 8:54GraphQL schema tools
- 10:20Queries and mutations
- 12:28Aliases and fragments
- 15:01GraphQL directives
- 18:32Interfaces and unions
- 21:21Pagination and sorting
- 25:18When to use GraphQL
- 31:25Q&A
related talks
49mGraphQL, different way to think about APIs
01h 00mGraphQL - A query language to empower your API consumers
31mGraphQL: how to make clients enjoy using your API
58mGraphQL -- Flexible APIs for Adaptive Clients
48mGraphQL Is the New Sexy
46mGraphQL 101 - Stop RESTing, Start Querying
54mGraphQL — Usable API or Just Another Hype?
28mExploring GraphQL