Do We Really Need GraphQL?
summary
Examines the strengths and weaknesses of GraphQL, discussing where GraphQL is useful and where it may fall short. Covers practical considerations and trade-offs when choosing GraphQL for an application.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 3:44About Pavel and GraphQL
- 6:32When GraphQL is needed
- 13:42GraphQL reducing data
- 15:49Code generation with GraphQL
- 20:27State updates and RPC
- 24:26Complex GraphQL queries
- 26:13GraphQL for server comms
- 29:46GraphQL fails: files
- 36:45Multi-user editing with CRDT
- 38:53GraphQL authentication
- 43:09GraphQL performance
- 44:34GraphQL subscriptions
- 45:19Complex GraphQL forms
- 47:49Mixed architectures
- 51:23GraphQL limitations
- 51:44Architecture lessons
- 53:09Summary and Q&A
related talks
23mHarnessing the Power of GraphQL
30mWhy GraphQL vs. Why not GraphQL
49mGraphQL - When a REST API Is Not Enough
54mGraphQL — Usable API or Just Another Hype?
51mGraphQL: What, How and When
51mGraphQL: advantages, challenges, and how to overcome them
01h 11mGraphQL: 'Dangerous' Advice. Why Use GraphQL When There’s REST?
18mWelcome to GraphQL