Graph-First Services Using GraphQL
summary
GraphQL schema drives service design, used at scale inside Twitter to unify many back ends and power a Network Health Visualizer. Implementation uses Sangria + Finatra and integrates in ~1 day and ~20 lines of code. Live tooling includes GraphiQL with tab‑completion and tracing; language features used are @defer and @stream, batching/caching via resolvers/DataLoader, complexity analyzer and depth limits, cache‑control extensions, and schema stitching/type extensions for service composition.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 1:09Modern data services challenges
- 3:02GraphQL as a universal API
- 5:15Sangria and Sinatra setup
- 7:28GraphiQL for API exploration
- 10:25Optimizing GraphQL queries
- 12:53Handling slow fields with defer
- 15:22Streaming lists with stream directive
- 16:50Preventing query complexity issues
- 19:21Caching in GraphQL
- 20:45Scaling with schema stitching
- 22:09Q&A and closing
related talks
48mGraphQL - a type system for your API
29mWhy You Should Use Implementation-First to Build Your GraphQL Schema
55mGraphQL - APIs the New Way
01h 00mGraphQL - A query language to empower your API consumers
23mAn Introduction to GraphQL
40mGraphQL: Designing a Data Language
47mIntroduction to Graphql
35mGraphQL in real life