Demand Driven Applications with GraphQL by Vinci Rufus
summary
Claim: GraphQL replaces brittle REST contracts by letting each component request exact fields so the API becomes a single endpoint that returns not more not less and reduces wasted payload. Concrete tooling and patterns: GraphiQL and Launchpad for live queries, graphql-tools mocking with casual, batching and cache fixes using DataLoader, and real-time subscriptions via WebSockets. Demo shows an Angular frontend backed by Graphcool where star-voting syncs across tabs, and common pitfalls like N+1 queries and auth placement get solved or shifted to specific layers.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:51Adhering to Jason Contracts
- 2:49Documentation
- 5:24What Graph Ql Is Not
- 6:20What Exactly Is Graph Ql
- 9:57The Graphical Schema
- 12:08Get Area
- 18:22Mutations
- 22:23Query Fragment
- 25:36Classic N + 1 Query Problem
- 27:22Data Loader
- 29:07Tenth Occasion and Authorization with Graph Ql
- 29:24Authorization and Authentication
- 37:51How Can I Selectively Show Certain Fields to a User Based on the Type
- 39:29The Server-Side Deployment
related talks
33mGraphQL - the What, how and why
19mGraphQL: Accelerating Digital Transformation Through Modern APIs.
58mGraphQL -- Flexible APIs for Adaptive Clients
49mGraphQL, different way to think about APIs
31mGraphQL: how to make clients enjoy using your API
23mHarnessing the Power of GraphQL
38mModernize your Angular apps with GraphQL
28mCurious Use Cases of GraphQL