GraphQL, the Domain Way
summary
Claims that GraphQL forces a schema-first domain model and gives product teams “superpowers” by letting them focus on domain logic rather than raw data, with resolvers keeping infrastructure separate. Example domain: recruiting, where a 20% cancel rate surfaces the real problem as coordinator workflow not interviewer behavior, so the model targets easy backup-fills. Shows a MongoDB resolver and how a one-request nested query replaces multiple REST calls, and highlights the GraphiQL documentation explorer and resolvers isolate infra pattern.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:10Defining Domain
- 4:17GraphQL Overview
- 7:18Strategy 1 Finding the Important Parts
- 11:19Strategy 2 The Schema
- 16:56Strategy 3 Shared Vocabulary
- 20:48Strategy 4 Documentation
- 21:58Recap
related talks
35mGraphQL in the Enterprise
23mHarnessing the Power of GraphQL
30mWhy GraphQL vs. Why not GraphQL
55mGraphQL - APIs the New Way
36mGraphQL Will Do To REST What JSON Did To XML
33mGraphQL - the What, how and why
01h 00mGraphQL - A query language to empower your API consumers
37mGraphQL — A New Look at the API