GraphQL
summary
GraphQL Ruby moves from anonymous procs to method resolvers and a class-based types API so fields inherit like Ruby methods, giving named stack traces, easier extension with super, and measurability. Learning the mistakes takes time — it takes about two years to discover procs are slower and hard to debug. The runtime still follows the spec but adds ergonomics: prefer short-lived objects for safety, plan feature-flagged execution and embedding execution alongside types.
AI-written summary · about
chapters (9)
- 0:00Start
- 5:15Query Language
- 6:59Runtime
- 9:06Type System
- 11:03The Spec
- 12:27Procs
- 13:55Data vs. Behavior
- 16:07Inheritance
- 17:06State
related talks
36mGraphQL Migration: A Proper Use Case for Metaprogramming?
23mGraphQL in real life
32mFrom learning to thinking in GraphQL
54mOptimizing performance in Rails apps with GraphQL layer
41mThe GraphQL Way: A new path for JSON APIs
18mWelcome to GraphQL
24mOptimizing for API Consumers with GraphQL
27mGraphQL Performance at Shopify