GraphQL, different way to think about APIs
summary
GraphQL claims to cut REST ping‑pong by letting clients ask for exactly the fields they need in a single request, proven in a live GraphiQL demo that pulls Twitter data and in GitHub’s Explorer; originated at Facebook 2012 and open sourced 2015. It exposes a typed schema, supports mutations for changes and an RFC for subscriptions, and works as an API gateway (Apollo, graphcool PHP examples) combining microservices into one queryable graph.
AI-written summary · about
chapters (17)
- 0:00Start
- 4:12FRAMEWORK FIRST!
- 4:41DATABASE FIRST!
- 5:42API FIRST!
- 6:39SO, WHERE TO START?
- 10:03UNIFORM INTERFACE
- 10:47STATELESS
- 11:09CLIENT SERVER
- 11:25LAYERED SYSTEM
- 16:17WHAT IS GRAPHQL?
- 17:16API QUERY LANGUAGE
- 17:27SERVER SIDE RUNTIME FOR QUERY EXECUTION USING DEFINED TYPE SYSTEM
- 24:20DEMO
- 33:01READS
- 33:12WRITES?
- 36:12CHANGE NOTIFICATION?
- 43:08ONE MORE THING.
related talks
37mGraphQL — A New Look at the API
58mGraphQL -- Flexible APIs for Adaptive Clients
33mGraphQL - the What, how and why
01h 00mGraphQL - A query language to empower your API consumers
48mGraphQL - a type system for your API
31mGraphQL: how to make clients enjoy using your API
28mExploring GraphQL
46mGraphQL 101 - Stop RESTing, Start Querying