Why GraphQL is Perfect for Microservices
summary
Claim: GraphQL becomes a single composable data layer over domain microservices, letting teams expose per-service schemas and combine them into a supergraph that a gateway load balances and queries. Two composition patterns are alive: schema stitching (custom resolvers) and Apollo Federation (supergraph + subgraphs); StepZen-style import lets non-federation services join without code changes. Proven: federated gateways handle multi-language services, keep one endpoint, enable incremental monolith→microservice migration, and reduce gateway churn.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:28Who is this talk for
- 2:51What makes a good microservice
- 5:11Microservice boundaries
- 7:55GraphQL
- 15:51GraphQL vs Rest
- 17:32GraphQL for Microservices
- 24:14Schema Stitching
- 28:12GraphQL Federation
- 36:57Why GraphQL and Microservices
- 43:10Conclusion
related talks
27mWhy GraphQL is Perfect For Microservices
37mGraphQL and Microservices or How we learned to be big and small at the same time
01h 13mFrom Monolith to Microservices and Back
50mDistributed GraphQL APIs: Breaking Down Monoliths & Unlocking Agility for Dev Teams
20mWhy GraphQL Between Microservices Is the Worst & Best Idea
06mEscape the GraphQL Monolith
08mGraphQL: everything you want in one query
48mApollo Federation: Connecting GraphQL Microservices