Optimizing for API Consumers with GraphQL
summary
GitHub adopts GraphQL as a client-first API layer, implements it on Rails with the GraphQL Ruby gem, exposes a single /graphql endpoint and runs 100 million queries every day. Demos show a local NYC restaurant grades API, live GraphiQL autocomplete, and generated docs via GraphQL Docs. Tooling includes a GraphQL Client gem and schema-driven development; resolver functions call ActiveRecord or any backend, and the public launch at GitHub Universe proves it works in production.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:25optimizing APIs for consumers...
- 3:54backends for frontends
- 4:55what about a public API?
- 5:17GraphQL is a specification
- 7:11features of the query language
- 10:58documentation and client generation, are free
- 14:54multiple resources in one round trip
- 15:23Implementing a GraphQL server
- 15:56like SQL, there are many implementations
- 19:20a facade in front of services
- 19:32you use your existing application code
- 20:43proof of concept done
- 21:42exchange a query for Ruby objects
- 22:00tooling
- 22:32schema driven development
- 23:35true platform
related talks
41mThe GraphQL Way: A new path for JSON APIs
36mGraphQL on Rails - Creating Living APIs for a Data-hungry World
12mWhy GraphQL?
27mGraphQL on Rails
54mOptimizing performance in Rails apps with GraphQL layer
23mAugmenting a Legacy REST API with GraphQL
01h 00mGraphQL - A query language to empower your API consumers
58mGraphQL -- Flexible APIs for Adaptive Clients