Apollo Federation: Connecting GraphQL Microservices
summary
Shows a working Apollo Federation setup that merges an AWS AppSync subgraph and an Apollo Server subgraph hosted in an Azure Function into one Gateway running in Lambda behind API Gateway, with queries inspected in Apollo Studio and CloudWatch. Uses AWS AppSync (Federation v1), Apollo Server (Federation v2), Apollo Gateway, Rover CLI for local composition and Apollo schema registry for managed composition. Key details: subgraphs must mark entities with keys and directives, composition auto‑generates the supergraph SDL, and type mismatches block composition while leaving the previous schema live.
AI-written summary · about
chapters (22)
- 0:00Start
- 2:32Graphql
- 6:53Add an Api Gateway
- 7:06Schema Stitching
- 8:31Apollo Federation
- 10:37Federated Architecture
- 14:01Fetch Related Data
- 15:25Resolve Reference
- 17:29Provides Directive
- 19:21Super Graph
- 20:21Schema Composition
- 21:11Query Execution
- 24:13Schema Composition Process
- 25:20If Polling Fails
- 26:34Local Schema Composition
- 28:26Create a Yaml File
- 29:08Breaking Composition
- 30:32Demo
- 31:04Versions of Apollo Federation
- 38:32Query Plan
- 39:53Summary
- 44:29The Difference between the Schema Stitching to Federation
related talks
28mBuilding a distributed graph w/ Apollo Federation
36mGraphQL Federation - The @key to Your Platform API Strategy
31mDesign Principles of Federated GraphQL
17mThe year ahead for GraphQL Federation: Combining APIs for the AI era.
06mEscape the GraphQL Monolith
08mGraphQL: everything you want in one query
51mWhy GraphQL is Perfect for Microservices
31mUsing Apollo Federation in a microservice architecture in Kubernetes