Building Distributed GraphQL APIs
summary
Shows a .NET demo using Hot Chocolate, Banana Cake Pop and Fusion to replace a monolithic GraphQL gateway with independently deployed subgraphs, composing schemas at build time and emitting query plans that reveal resolver steps. Demonstrates batching to turn N per-item subrequests into two optimized calls, working subscriptions across subgraphs via GraphQL over WS, and hot-reload Gateway configs. Claims developer scale benefits and cites a customer drop from 120 Apollo pods to 30 Fusion pods while keeping single-endpoint GraphQL for clients.
AI-written summary · about
chapters (17)
- 0:00Distributed GraphQL APIs intro
- 1:02Why GraphQL was invented
- 8:57GraphQL data fetching changes
- 13:18GraphQL fundamentals
- 19:07Building simple GraphQL server
- 20:34GraphQL monolith limitations
- 24:12Microservices scaling pros/cons
- 26:21When to use distributed GraphQL
- 29:30GraphQL Gateway over infrastructure
- 33:01Distributed GraphQL with subgraphs
- 35:36Demo: Composing GraphQL Gateway
- 44:10Optimizing query plans
- 47:06Real-time GraphQL setup
- 52:31Subscriptions with Fusion Gateway
- 55:03Best practices like Node pattern
- 58:20GraphQL Foundation updates
- 59:03Q&A: Fusion vs Apollo Federation
related talks
56mDistributed GraphQL APIs
50mDistributed GraphQL APIs: Breaking Down Monoliths & Unlocking Agility for Dev Teams
59mBuilding Distributed GraphQL APIs
30mGraphQL Fusion Rethinking Distributed GraphQL
59mBuilding GraphQL APIs in C#
57mBuilding modern applications with GraphQL 2021 and beyond in ASP.NET Core 6
41mGraphQL: The Good Parts
01h 04mHot Chocolate: An introduction to GraphQL on ASP.Net Core
