GraphQL - the What, how and why
summary
Claim: GraphQL replaces multiple REST endpoints with a single endpoint returns requested shape so queries dictate the JSON returned and mutations both write and return data. Demo uses Graphcool: define schema, run Graphcool CLI deploy, get a CRUD GraphQL server. Compares clients: Apollo vs Relay (Apollo easier, Relay more optimized). Notes: production users include Coursera GitHub Shopify Pinterest New York Times Twitter, GraphQL Summit ~600 attendees, Graphcool Slack ~6,000 members.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:36What is GraphQL
- 2:50Companies using GraphQL
- 3:16Example
- 3:39REST API
- 7:14GraphQL Post Request
- 8:33GraphQL Queries
- 9:43Query Shape
- 10:36Mutations
- 11:44GraphQL Schema
- 13:36GraphQL
- 16:27Reactive GraphQL
- 17:32Declarative Programming
- 19:05DomainSpecific Languages
- 20:35React
- 22:06Why GraphQL
- 23:16Summary
- 24:05Graphical Client Libraries
- 25:56Relay vs Apollo Client
- 29:18demo
- 31:19Resources
related talks
49mGraphQL, different way to think about APIs
58mGraphQL -- Flexible APIs for Adaptive Clients
37mGraphQL — A New Look at the API
01h 00mGraphQL - A query language to empower your API consumers
28mExploring GraphQL
54mGraphQL — Usable API or Just Another Hype?
46mGraphQL 101 - Stop RESTing, Start Querying
31mGraphQL: how to make clients enjoy using your API