Entities in Apollo Federation

In a supergraph, an entity is an object type that can resolve its fields across multiple subgraphs. Each subgraph can contribute different fields to the entity and is responsible for resolving only the fields that it contributes.

For example, this Product entity's fields are defined and resolved across two subgraphs:

type Product @key(fields: "id") {
  id: ID!
  name: String!
  price: Int
}

type Product @key(fields: "id") {
  id: ID!
  inStock: Boolean!
}

Entities are a fundamental building block of Apollo Federation that enable subgraphs to adhere to the

Defining an entity

To define an entity within a particular subgraph, you do the following:

1. Apply the
   @key directive
   to an object type.
2. Define the object type's
   reference resolver
   .

These steps are described below.

1. Define a @key

In a subgraph schema, you can designate any existing object type as an entity by adding the @key directive to its definition, like so:

1
type Product @key(fields: "id") {
2
  id: ID!
3
  name: String!
4
  price: Int
5
}

The @key directive defines an entity's unique key, which consists of one or more of the type's fields. In the example above, the Product entity's unique key is its id field. Every instance of an entity must be uniquely identifiable by its @key fields. This is what enables your router to associate field data from different subgraphs with the same entity instance.

In most cases, the @key field(s) for the same entity will be the same across subgraphs. For example, if one subgraph uses id as the @key field for the Product entity, other subgraphs should do the same. However, this

If coming from a database context, it can be helpful to think of a @key as an entity's

type Product @key(fields: "id") {
  id: ID!
  name: String!
  price: Int
}

type Product @key(fields: "id") {
  id: ID!
  inStock: Boolean!
}

An entity's @key cannot include:

• Fields that return a union or interface
• Fields that take arguments

Though not strictly required, it's best to use non-nullable fields for keys. If you use fields that return null values, GraphOS may encounter issues resolving the entity.

For more information on advanced key options, like how to define

2. Define a reference resolver

The @key directive effectively tells the router, "This subgraph can resolve an instance of this entity if you provide its unique key." In order for this to be true, the subgraph needs to define a reference resolver for the entity.

For the Product entity defined

1
// Products subgraph
2
const resolvers = {
3
  Product: {
4
    __resolveReference(productRepresentation) {
5
      return fetchProductByID(productRepresentation.id);
6
    }
7
  },
8
  // ...other resolvers...
9
}

Let's break this example down:

• You declare an entity's reference resolver in your resolver map, as a member of the entity's corresponding object.
• A reference resolver's name is always __resolveReference.
• A reference resolver's first parameter is a representation of the entity being resolved.
  • An entity representation is an object that contains the entity's @key fields, plus its __typename field. These values are automatically provided to your subgraph by your router.
• A reference resolver is responsible for returning all of the entity fields that this subgraph defines.
  • In this example, the hypothetical fetchProductByID function fetches a particular Product's field data based on its id.

Every subgraph that contributes at least one unique field to an entity must define a reference resolver for that entity.

To learn more about __resolveReference in Apollo Server, see the

Contributing entity fields

Any number of different subgraphs can contribute fields to an entity definition. Below, the Products and Inventory subgraphs contribute different fields to the Product entity:

type Product @key(fields: "id") {
  id: ID!
  name: String!
  price: Int
}

type Product @key(fields: "id") {
  id: ID!
  inStock: Boolean!
}

When a subgraph contributes entity fields, no other subgraph knows about those fields—only the router does thanks to the composed supergraph schema.

By default, each subgraph must contribute different fields, with the important exception of @key fields. Otherwise, a composition error occurs. To override this default, see

As mentioned previously, each subgraph that does contribute fields to an entity must

Referencing an entity without contributing fields

Your subgraphs can use an entity as a field's return type without contributing any fields to that entity. This requires less code than the steps in

Take a look at this Product entity in the Products subgraph:

1
type Product @key(fields: "id") {
2
  id: ID!
3
  name: String!
4
  price: Int
5
}

Now, let's say we want to create a Reviews subgraph that includes the following Review type:

1
type Review {
2
  product: Product!
3
  score: Int!
4
}

This is possible. However, this subgraph schema is currently invalid because it doesn't define the Product entity.

To fix this, we can add a stub of the Product entity to the Reviews schema, like so:

1
type Review {
2
  product: Product!
3
  score: Int!
4
}
5

6
type Product @key(fields: "id", resolvable: false) {
7
  id: ID!
8
}

As you can see, this stub definition includes only the @key fields of Product (just id in this case). It also includes resolvable: false in the @key directive to indicate that this subgraph doesn't even define a reference resolver for the Product entity.

Example query flow

To help understand how entities are resolved across subgraphs, let's look at an example query executed on an example supergraph.

Let's say we have these two subgraphs that both define the Product entity:

type Product @key(fields: "id") {
  id: ID!
  name: String!
  price: Int
}

type Product @key(fields: "id", resolvable: false) {
  id: ID!
}

type Review {
  score: Int!
  description: String!
  product: Product!
}

type Query {
  latestReviews: [Review!]!
}

The Reviews subgraph defines one entry point into our schema: Query.latestReviews. This means that the following query is valid against our router:

1
query GetReviewsWithProducts {
2
  latestReviews { # Defined in Reviews
3
    score
4
    product {
5
      id
6
      price # ⚠️ NOT defined in Reviews!
7
    }
8
  }
9
}

Here we have a problem: this query needs to start its execution in the Reviews subgraph (because that's where latestReviews is defined), but that subgraph doesn't know that Product entities have a price field. Remember, the Reviews subgraph only knows about the id field of Product.

Because of this, the router needs to fetch price from the Products subgraph instead. To handle this two-step process, the router generates a query plan.

The query plan

A query plan is a blueprint for dividing a single incoming operation into one or more operations that are each resolvable by a single subgraph. Your router generates a query plan for each unique operation that it receives from clients.

With our example query above, the router knows the following:

• It must start by querying the Reviews subgraph, because that's where Query.latestReviews is defined.
• It must then query the Products subgraph to fetch the price of each Product returned by the Reviews subgraph.

Using this information, the router's query plan starts with this query to the Reviews subgraph:

1
query {
2
  latestReviews {
3
    score
4
    product {
5
      __typename
6
      id
7
    }
8
  }
9
}

Notice that this query omits the Product.price field but adds the Product.__typename field. This is because the router needs representations of each returned Product entity for its second query.

This first query returns a list of Review objects, each containing a Product representation. With these representations, the router can execute its second query, this time on the Products subgraph:

1
query {
2
  _entities(representations: [...]) {
3
    ... on Product {
4
      price
5
    }
6
  }
7
}

This query uses a special entry point that's automatically added to every subgraph schema: Query._entities. This entry point is what provides the router with direct access to any entity's fields.

Each item in the representations list argument above is one of the Product representations that the router obtained from its first query. Here's an example list:

1
[
2
  {
3
    "__typename": "Product",
4
    "id": "1"
5
  },
6
  {
7
    "__typename": "Product",
8
    "id": "2"
9
  },
10
  //...
11
]

These representations are passed individually to the Product

1
[
2
  {
3
    "price": 100
4
  },
5
  {
6
    "price": 200
7
  },
8
  //...
9
]

Nice! The router can merge this price data with the Product objects returned by its first query. After doing so, the router returns a single, combined result to the client.

Advanced topics

See