Building APIs you want to hug with GraphQL
summary
Argues for schema-first GraphQL design using the graphql-ruby gem, models a Dungeons & Dragons domain (5th ed rulebook, 316 pages) to show concrete types: playerCharacter, race, playerClass, and an ability_score node; recommends non-null scalars and enums, prototyping resolvers without persistence, keeping fields minimal, moving business logic server-side, and running graph modeling sessions with domain experts. Shows a working schema-driven prototype that proves easier evolution and cross-discipline collaboration.
AI-written summary · about
chapters (11)
- 0:00Start
- 5:10Building huggable APIs.
- 5:31Good Schema Design.
- 9:47Model Relationships.
- 14:08Use enums for fields with a fixed set of allowed values.
- 16:31Think use-cases.
- 18:19Thinking in Graphs.
- 18:52Modelling your own domains.
- 19:28Keep the scope small.
- 19:49Model the domain, not the feature.
- 20:13Involve Domain Experts.
related talks
41mThe GraphQL Way: A new path for JSON APIs
36mGraphQL on Rails - Creating Living APIs for a Data-hungry World
25mGraphQL, the Domain Way
24mOptimizing for API Consumers with GraphQL
36mGraphQL Migration: A Proper Use Case for Metaprogramming?
22mGraphQL for Everyone
27mAuthorization in the GraphQL era
27mGraphQL on Rails