GraphQL Federation
Multiple services own disjoint schema fragments; each declares entities with `@key` fields, extends types owned elsewhere, and a router composes one supergraph, planning cross-service queries that join entities via reference resolvers. This replaces schema stitching and keeps one graph without one monolith.
This Concept is waiting for its first lesson!
Multiple services own disjoint schema fragments; each declares entities with `@key` fields, extends types owned elsewhere, and a router composes one supergraph, planning cross-service queries that join entities via reference resolvers. This replaces schema stitching and keeps one graph without one monolith.
Are you a teacher? Sign in to start contributing.
Sign In