GraphQL in real life
summary
GraphQL powers a New York Times feature and solves multiple-endpoint latency by letting clients request exactly the fields they need; Android uses Apollo for compile time safety, generated Java types, caching and automatic persisted queries to shrink requests under an 8 kilobyte limit imposed by the CDN. Testing relies on MockWebServer to replay real responses. Tooling includes GraphiQL, Graphcool, Altair and Insomnia for schema-driven query authoring and debugging, and persistent queries prove the approach works in production.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:40Rest and GraphQL
- 3:23GraphQL vs Kotlin
- 4:44GraphQL conventions
- 5:46Versioning
- 7:27RESTful API
- 8:36GraphQL caching
- 9:10GraphQL parameters
- 10:11Multiple endpoints
- 11:48Unified response
- 12:57GraphQL
- 13:47Query
- 15:09Other tools
- 19:29Apollo
- 23:20The downside
- 23:45Testing
- 25:00Problem
- 26:30Automatic persistent queries
- 33:52Something isnt know
