GraphQL — Closing a Profitable Contract Between Server and Client
summary
GraphQL is presented as a way to replace many REST endpoints with a single typed query language, enabling static analysis on the client via schema introspection, generated type definitions and Flow/TypeScript checks to eliminate runtime type errors. The talk covers server-side patterns like DataLoader for N+1 problems, query cost checks and persisted queries, and describes tooling built (graphql-compost and a watcher) that auto-generates types — an example run produced 10,000 types and about 700 lines of integration code, with a month-long migration across ~500 files that reduced bugs and network requests.
AI-written summary · about
chapters (6)
- 0:00GraphQL introduction
- 10:11GraphQL basics
- 21:26GraphQL vs REST
- 30:21GraphQL challenges
- 42:30Schema tools
- 50:47Q&A
related talks
37mGraphQL — A New Look at the API
32mFrom learning to thinking in GraphQL
30mWhy GraphQL vs. Why not GraphQL
31mGraphQL: how to make clients enjoy using your API
58mGraphQL -- Flexible APIs for Adaptive Clients
54mGraphQL — Usable API or Just Another Hype?
03h 00mUnderstanding GraphQL
23mHarnessing the Power of GraphQL