About this deal
For this quickstart, you can keep the default suggested variant name or change it to anything else you like (e. For every variant of a cloud supergraph , GraphOS provisions and manages a router that acts as the variant 's public endpoint. Many will say that federation is the overall winner, as it allows teams to focus on their application without needing to maintain a gateway. You only need to provide a subgraph 's --routing-url the first time you publish that subgraph 's schema to a particular variant (unless you need to change that URL later).
It's also responsible for combining multiple subgraph responses into a single response for the client.Familiarizing yourself with fundamental GraphQL concepts is an important prerequisite to getting the most out of your supergraph . GraphQL schema federation works by bringing schemas together for a more unified way to access and query data.
GraphQL's built-in introspection query is the fastest way for bad actors to learn about your schema . Hivee, an upstart modern supermarket chain, also uses a supergraph to unite its investment into APIs. To enhance the utility of traces collected in your observability tooling, it's a best practice to require every client to identify itself and assign a name to every operation it executes.
Before we try executing operation s on your supergraph , we need to make sure your router is set up to communicate successfully with both your clients and your subgraph . Just as React and Kubernetes leverage modularity to scale UI development and service deployment, the supergraph leverages modularity to scale the API layer as it grows beyond a single team. This tracing data is included in the extensions key of the response from a subgraph to the router , where the data is aggregated into a trace shape based on the query plan and then sent to GraphOS .