Databases in the Jamstack
summary
Argues that databases belong behind an API layer so Jamstack sites use databases without ops work, demonstrating a Next.js demo app that reads and writes to a Hasura GraphQL backend via Netlify functions triggered by Netlify forms. Uses XState for state, environment variables for Hasura admin keys, and simple GraphQL queries; form submissions create rows in Hasura and a random-character query returns them. Shows thousands-concurrent submissions with low latency and no server maintenance.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:40Jamstack
- 1:56APIs
- 3:47Sites
- 5:37Database API
- 8:09Adventure
- 10:13Serverless Functions
- 16:56Live QA
- 20:03Hydration
- 21:25Serverless vs GraphQL
- 23:33Web Ecosystem
- 25:41Domain Lag
- 27:12Audience Questions
related talks
28mModernizing App Development: Planet-scale GraphQL & Distributed SQL
28mNext.js and Prisma: Databases in Serverless Made Easy
20mSuperpowers Developers: GraphQL + DistributedSQL
19mBuilding Planet Scale Cloud Native Apps with GraphQL & Distributed SQL
17mHasura: a GraphQL back-end in minutes
34mEnabling data at massive scale with Next.js
08mWhen Worlds Collide: Frontend vs Database
09mAdding a GraphQL backend to your Jamstack app with Fauna
