Join us for GraphQL Summit, October 10-12 in San Diego. Use promo code ODYSSEY for $400 off your pass.
Launch GraphOS Studio

Supergraph next steps

Get the most out of GraphOS

After you create a supergraph with Apollo Studio, read below to learn about some of the next steps you should take to get the most out of it and the entire platform.

For the most part, you can perform these next steps in any order. But you should definitely start by installing the Rover CLI.

First, install the Rover CLI!

The CLI is the primary command-line interface for interacting with . You'll use Rover both locally and in CI environments to perform a variety of actions on your and its individual s.

Install Rover, then return to this article.

Run your supergraph locally

See this article.

Subgraph actions

Update a subgraph schema

When you first set up your cloud , Apollo Studio fetches your existing GraphQL API's . Your existing API becomes the first subgraph in your :

Your infrastructure
Subgraph A
(Your GraphQL API)

This initial fetch is a one-time action to help you get started. Whenever your API's schema changes, Studio doesn't automatically fetch it again. This means your doesn't know about those changes. Clients can't include any new s in their queries until your does know about the changes!

Whenever you update your 's , you need to publish those changes with the CLI. Learn about publishing subgraph schemas.

After learning about the publishing process, you should integrate it into your CI workflow.

Add another subgraph

One of the most powerful features of a is that it can combine multiple GraphQL APIs into a single graph:

Your infrastructure
Subgraph A
Subgraph B
Subgraph C

With this architecture, different teams in your organization can each maintain their own . This helps teams work in parallel, because they aren't all contributing to the same single codebase.

1. Build your new subgraph

See Creating a new subgraph.

2. Add the subgraph to your supergraph

See Adding a new subgraph.

Add another variant

Most s have multiple variants, each of which represents that running in a different environment (production, staging, and so on).

If your runs in multiple environments, you sould create a different for each.

Learn how to create variants.

Enable federation features

s use an architecture called Apollo Federation. Federation is at its most powerful when your s share responsibility for some of your 's types, instead of defining mutually exclusive types and s.

To take full advantage of federation features, each of your s needs to use a GraphQL server library that conforms to the Apollo Federation subgraph specification. Fortunately, many popular server libraries do!

  1. To check whether your current GraphQL server library supports the specification, see this article.
    • If your library does support the spec, consult its documentation to learn how to enable its federation support. For Apollo Server, see this article.
    • If your library doesn't support the spec, consult the library list to find an alternative in your preferred programming language.
  2. Enable federation support for all of your s and deploy the updated subgraphs to your environment.

After you make these changes, you can start using powerful federation features in your s, including:

Set up continuous delivery

Every time you want to make changes to one of your s, you should do the following:

  1. Verify that your proposed changes won't break your or any of your existing clients.
  2. Whenever you deploy verified changes, always publish your updated to as part of that deployment.

Disable client-subgraph communication

With a architecture, clients should never query your individual s directly. Instead, they should always query the ! This means your subgraphs can (and should) reject incoming requests from any source besides the .

Your infrastructure
Subgraph A
(Your GraphQL API)

How you choose to configure this access control depends on your GraphQL server library and your particular infrastructure.

Make sure any existing clients that communicate directly with your API are updated to communicate with your before you begin rejecting direct requests!

For more information, see Securing your subgraphs.

Studio actions

Configure notifications

can send you various types of notifications via a few different channels (including Slack and Pagerduty). These notifications can include a daily metrics report, change updates, and experimental performance alerts. Set up notifications.

Invite team members

If you've created a Studio organization to collaborate with your team, invite your team members from the organization's Members tab.

Client actions

Add identification headers to your clients

A 's Clients page enables you to view metrics, segmented by your different clients:

Client awareness overview

To get the most out of this feature, each of your client applications should set values for the following HTTP headers in each request they send to your :

  • apollographql-client-name
  • apollographql-client-version
Self-hosted setup
Creating a new subgraph
Edit on GitHubEditForumsDiscord