Schema Driven Development
summary
Claim: a runnable GraphQL service is created from scratch with no backend code by dropping a schema and a config into Juxt's Site. Uses GraphQL SDL, Site server, the Juxt grab library and XTDB via an eden config; GraphiQL is used to exercise queries and mutations. A pets app is implemented in ~15 minutes: queries, add/update/delete mutations, a generated id flow, duplicate handling and XTDB time-travel history all work, and assets remain served via REST.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:17Getting an access token
- 5:27Using xtdb
- 7:49Writing the schema
- 14:57Adding mutations
- 15:10Updating and deleting pets
- 18:24Entity History
- 19:17Recap
related talks
08mWhen (Not) To Create A GraphQL Server
25mThe Intersection of GraphQL & Design Systems in Product Dev.
27mHow GraphQL Gives Coding Agents Eyes on What Actually Matters
32mFrom learning to thinking in GraphQL
29mClosing the Loop: How GraphQL Gives Coding Agents Eyes on What Actually Matters
41mDemand Driven Applications with GraphQL by Vinci Rufus
24mGoing GraphQL
01h 28mWorkshop: Demand-Driven Schema Design