Accelerating GraphQL API Development with Schema Storming and Code-first Implementation
summary
Claims that code-first classes plus test-driven checks solve resolver/schema drift and that visual schema storming workshops produce precise UI-to-schema fragments. Demo uses TypeGraphQL and live test runner wabby to assert a service outputs the expected SDL and to prevent pushing schemas with no resolvers. Built an internal tool that stores UI annotations, query fragments and specs; works at scale — cited roughly 100 subgraphs and 3,000 types with automated fragment-to-subgraph wiring and an AI-assisted query generator.
AI-written summary · about
chapters (12)
- 0:00Introduction and journey
- 2:33Schema first vs code first
- 4:21Introducing schema storming
- 7:14Three steps of schema storming
- 11:33Team collaboration with schema
- 14:03Adding new components to schema
- 16:10Legacy systems and GraphQL
- 17:54Schema first to code first
- 19:21Code first with test-driven development
- 23:45Testing schema and resolvers
- 26:36Tooling for schema collaboration
- 28:45Future of schema development
related talks
27mThe Benefits of Code First Over Schema First in GraphQL
23mBlueprints of Successful GraphQL Architectures
22m8 Years of GraphQL: Unraveling the Trade-Offs
27mThe ultimate GraphQL client development experience
16mHow I Started Mocking My GraphQL Schema
25mGraphQL, the Domain Way
28mTeach Yourself GraphQL in 2026: An Anti-blueprint
16mIntro to GraphQL