GraphQL Summit is back for three days of insights, hands-on learning, and fun to celebrate the GraphQL community. Join us in San Diego Oct 3-5.
Try Apollo Studio

Federation quickstart

Part 4 - Working with subgraphs

In the previous parts of this quickstart, we used Apollo-hosted services for our subgraphs. Now, let's see what we can do with our own subgraphs.

Our subgraphs can use any GraphQL server library that supports Apollo Federation. This includes Apollo Server, along with the other libraries listed in Federation-compatible subgraph implementations.

1. Configure Apollo Server

If you're using a GraphQL server besides Apollo Server, consult its documentation to learn how to configure it for use as a subgraph.

If you have an existing GraphQL API that uses Apollo Server, you can use that server as a subgraph with the @apollo/subgraph library. You can get started with this example server (which is not yet federated).

First, install the latest version of the @apollo/subgraph library in your project:

npm install @apollo/subgraph

Next, import the buildSubgraphSchema function in the file where you initialize ApolloServer:

const { buildSubgraphSchema } = require('@apollo/subgraph');

Finally, modify your ApolloServer constructor by passing it a schema option instead of typeDefs and resolvers, like so:

const server = new ApolloServer({
schema: buildSubgraphSchema({ typeDefs, resolvers })

(As shown, you now pass your typeDefs and resolvers to buildSubgraphSchema.)

And that's it! You can now perform all of the same subgraph setup on your own service (schema publishing, introspection, etc.) that you did with the Apollo-hosted services we used in the previous parts. Refer to those parts for guidance.

2. Learn about federated types

In a federated graph, each subgraph's schema can define or reference types and fields that are also present in another subgraph's schema.

Consider the Location type in our composed supergraph schema from Part 3. This type includes the following fields:

type Location
@join__type(graph: LOCATIONS, key: "id")
@join__type(graph: REVIEWS, key: "id")
id: ID!
"""The name of the location"""
name: String! @join__field(graph: LOCATIONS)
"""A short description about the location"""
description: String! @join__field(graph: LOCATIONS)
"""The location's main photo as a URL"""
photo: String! @join__field(graph: LOCATIONS)
"""The calculated overall rating based on all reviews"""
overallRating: Float @join__field(graph: REVIEWS)
"""All submitted reviews about this location"""
reviewsForLocation: [Review]! @join__field(graph: REVIEWS)

As the federation-specific @join__field directive suggests, these fields of the same object type are defined across two different subgraphs!

This is possible because our Locations subgraph schema defines the Location object type as an entity. Entities are object types that multiple subgraphs can contribute fields to.

It makes logical sense that the reviews field of a Location should be resolved by the Reviews subgraph instead of the Locations subgraph. This reflects the design principle of separation of concerns.

Learn how to work with entities.

3. Try out schema checks

After you've registered your first subgraph schema, you can try out one of Apollo Studio's most powerful features: schema checks.

With schema checks, you can check whether some changes you want to make to your schema will affect any of the existing clients that use your supergraph. This feature is at its most powerful in your CI/CD environment, where you can automatically detect breaking schema changes before they're deployed to production.

  1. Learn about the basics of schema checks
  2. Learn about using schema checks with Apollo Federation
  3. Learn how to use Rover in a CI/CD environment

Congratulations, you've completed the federation quickstart! If you have any feedback or suggestions for this tutorial, please click Rate article on the right.

Edit on GitHub
3️⃣ Local composition