Choosing a GraphQL provider - A tale of trade-offs
summary
Compares PostgreSQL-backed providers like PostgreSQL-backed providers and Hasura style DB layers versus SaaS APIs, shows how deep relational queries map to performance and consistency tradeoffs (example: a money-transfer mutation flips balances 300/200 then reads still show old 200 under eventual consistency). Demonstrates query costing (GitHub-style cost 550 and 20,000 complexity points), differences in mutation patterns (nested transactional vs single-step), realtime via subscriptions or webhooks, and composition options like Apollo Federation 2 and the tension transactions vs eventual consistency.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:20What is GraphQL
- 2:29Understanding your problem
- 3:18Overview
- 4:05Data
- 5:57GraphQL providers
- 9:40Consistency
- 13:25Query maturity
- 18:30Query complexity
- 23:30Mutations
- 26:55Inserting data
- 28:55Subscriptions
- 31:15Flexibility
- 34:25Integration
- 36:45Checklist
related talks
28mModernizing App Development: Planet-scale GraphQL & Distributed SQL
51mGraphQL: advantages, challenges, and how to overcome them
23mHarnessing the Power of GraphQL
18mEmpowering Kubernetes Workloads with GraphQL
23mOpen Source, Graphs and GraphQL: The next frontier of modern applications
19mBuilding Planet Scale Cloud Native Apps with GraphQL & Distributed SQL
45mBuilding Scalable APIs: PostgreSQL Meets GraphQL
54mGraphQL — Usable API or Just Another Hype?