Claude Code for GraphQL Federation: Schemas, Subgraphs, and Router Config — Claude Skills 360 Blog
Blog / API / Claude Code for GraphQL Federation: Schemas, Subgraphs, and Router Config
API

Claude Code for GraphQL Federation: Schemas, Subgraphs, and Router Config

Published: December 2, 2026
Read time: 10 min read
By: Claude Skills 360

Apollo Federation 2 composes multiple GraphQL subgraphs into a single unified supergraph. Each microservice owns its slice of the schema, declares entity keys, and extends types owned by other services. The Apollo Router (Rust-based) routes queries to subgraphs based on the query plan. Claude Code designs subgraph schemas with @key, @external, @requires, and @provides directives, implements entity resolvers, configures the Apollo Router, and writes the federation integration tests.

CLAUDE.md for Federation Projects

## Federation Stack
- Apollo Federation 2.7 (spec 2.4+)
- Router: Apollo Router 1.x (Rust-based, replaces Apollo Gateway)
- Subgraph server: Apollo Server 4 + @apollo/subgraph
- Schema composition: rover CLI (local) + GraphOS Studio (CI)
- Subgraph services: orders-subgraph, users-subgraph, inventory-subgraph, payments-subgraph
- Client: Apollo Client 3 or URQL v4
- Testing: jest + @apollo/subgraph-testing-utils for subgraph unit tests
- Each subgraph owns its primary entities — no cross-subgraph extends for primary keys

Subgraph 1: Users

# users-subgraph/schema.graphql
extend schema
  @link(url: "https://specs.apollo.dev/federation/v2.4", import: ["@key", "@shareable"])

type Query {
  user(id: ID!): User
  me: User
}

type User @key(fields: "id") {
  id: ID!
  email: String!
  name: String!
  # avatarUrl is expensive — only resolve if explicitly selected
  avatarUrl: String @external
  createdAt: DateTime!
}

# Value type: shared by all subgraphs (no @key — not an entity)
type Address @shareable {
  street: String!
  city: String!
  country: String!
  postalCode: String!
}

scalar DateTime
// users-subgraph/src/resolvers.ts
export const resolvers = {
    Query: {
        user: async (_, { id }, { dataSources }) =>
            dataSources.usersAPI.getUser(id),
        me: async (_, __, { user }) => user,
    },
    
    User: {
        // Entity resolver — called when another subgraph references User by key
        __resolveReference: async ({ id }, { dataSources }) =>
            dataSources.usersAPI.getUser(id),
    },
};

Subgraph 2: Orders

# orders-subgraph/schema.graphql
extend schema
  @link(url: "https://specs.apollo.dev/federation/v2.4",
        import: ["@key", "@external", "@requires", "@provides"])

type Query {
  order(id: ID!): Order
  ordersByUser(userId: ID!, first: Int = 20, after: String): OrderConnection!
}

type Mutation {
  createOrder(input: CreateOrderInput!): CreateOrderPayload!
  cancelOrder(id: ID!, reason: String): Order!
}

type Order @key(fields: "id") {
  id: ID!
  # user field: stub — actual User data resolved by users-subgraph
  user: User!
  status: OrderStatus!
  items: [OrderItem!]!
  totalCents: Int!
  createdAt: DateTime!
  updatedAt: DateTime!
}

type OrderItem {
  product: Product!
  quantity: Int!
  unitPriceCents: Int!
}

# Stub for User entity — orders-subgraph knows userId internally
type User @key(fields: "id", resolvable: false) {
  id: ID!
}

# Stub for Product — provided by inventory-subgraph
type Product @key(fields: "id") {
  id: ID!
  # @requires: fetch these fields from inventory-subgraph before resolving subtotal
  price: Int @external
  # @provides: order items can tell the router that product.name is pre-populated
  name: String @external
}

enum OrderStatus {
  PENDING
  PROCESSING
  SHIPPED
  DELIVERED
  CANCELLED
}

type OrderConnection {
  edges: [OrderEdge!]!
  pageInfo: PageInfo!
  totalCount: Int!
}

type OrderEdge {
  cursor: String!
  node: Order!
}

input CreateOrderInput {
  userId: ID!
  items: [OrderItemInput!]!
}

type CreateOrderPayload {
  order: Order
  userErrors: [UserError!]!
}
// orders-subgraph/src/resolvers.ts
export const resolvers = {
    Query: {
        order: async (_, { id }, { db }) => db.orders.findById(id),
        ordersByUser: async (_, { userId, first, after }, { db }) =>
            db.orders.paginatedByUser(userId, first, after),
    },
    
    Mutation: {
        createOrder: async (_, { input }, { db, pubsub }) => {
            const order = await db.orders.create(input);
            pubsub.publish('ORDER_CREATED', { orderCreated: order });
            return { order, userErrors: [] };
        },
    },
    
    Order: {
        // Entity resolver: called when orders-subgraph is asked to resolve an Order by id
        __resolveReference: async ({ id }, { db }) => db.orders.findById(id),
        
        // Return stub object — users-subgraph resolves the full User
        user: (order) => ({ __typename: 'User', id: order.userId }),
        
        // items with product stubs — inventory-subgraph resolves full Product
        items: async (order, _, { db }) => {
            const items = await db.orderItems.byOrder(order.id);
            return items.map(item => ({
                ...item,
                product: { __typename: 'Product', id: item.productId },
            }));
        },
    },
};

Subgraph 3: Inventory contributing to Order

# inventory-subgraph/schema.graphql
extend schema
  @link(url: "https://specs.apollo.dev/federation/v2.4",
        import: ["@key", "@external", "@requires"])

type Query {
  product(id: ID!): Product
  products(ids: [ID!]!): [Product!]!
}

type Product @key(fields: "id") {
  id: ID!
  name: String!
  description: String
  price: Int!         # cents
  stockCount: Int!
  sku: String!
}

Apollo Router Configuration

# router.yaml
supergraph:
  path: /graphql

sandbox:
  enabled: false  # Disable in production

cors:
  origins:
    - https://myapp.com
    - https://admin.myapp.com

headers:
  all:
    request:
      - propagate:
          matching: ^x-
      - insert:
          name: x-router-id
          value: apollo-router

authentication:
  router:
    jwt:
      jwks:
        - url: https://auth.myapp.com/.well-known/jwks.json

authorization:
  directives:
    enabled: true

# Demand control: prevent expensive queries
preview_demand_control:
  enabled: true
  mode: enforce
  strategy:
    cost_per_field: 1
    default_budget: 1000

# Per-subgraph circuit breaking
traffic_shaping:
  all:
    deduplicate_query: true
    experimental_http2: negotiated
    timeout: 30s
  subgraphs:
    users:
      timeout: 5s
    orders:
      timeout: 10s
    inventory:
      timeout: 5s
      experimental_retry:
        min_per_sec: 10
        ttl: 10s
        retry_mutations: false

telemetry:
  exporters:
    tracing:
      otlp:
        endpoint: http://otel-collector:4318
        protocol: http
  instrumentation:
    spans:
      router:
        attributes:
          graphql.operation.type: true
          graphql.operation.name: true

Federation Integration Test

// tests/federation.test.ts
import { buildSubgraphSchema } from '@apollo/subgraph';
import { ApolloServer } from '@apollo/server';
import { addMocksToSchema } from '@graphql-tools/mock';

async function createTestSubgraph(typeDefs: DocumentNode, resolvers: object) {
    const schema = buildSubgraphSchema({ typeDefs, resolvers });
    const server = new ApolloServer({ schema });
    await server.start();
    return server;
}

it('resolves User entity from orders-subgraph', async () => {
    const { ordersServer } = await setup();
    
    const response = await ordersServer.executeOperation({
        query: `
            query ($representations: [_Any!]!) {
                _entities(representations: $representations) {
                    ... on Order {
                        id
                        status
                        user { id }
                    }
                }
            }
        `,
        variables: {
            representations: [{ __typename: 'Order', id: 'ord_123' }],
        },
    });
    
    expect(response.body.kind).toBe('single');
    expect(response.body.singleResult.errors).toBeUndefined();
    const order = response.body.singleResult.data!._entities[0];
    expect(order.user.__typename).toBe('User');
});

For the underlying GraphQL server patterns before adding federation, see the GraphQL guide for resolver design and schema-first development. For the subscription handling in federation where the router passes real-time events, the WebSocket scaling guide covers pub/sub infrastructure. The Claude Skills 360 bundle includes GraphQL Federation skill sets covering subgraph design, entity resolution, and Apollo Router configuration. Start with the free tier to try federation subgraph generation.

Keep Reading

AI

Claude Code for email.contentmanager: Python Email Content Accessors

Read and write EmailMessage body content with Python's email.contentmanager module and Claude Code — email contentmanager ContentManager for the class that maps content types to get and set handler functions allowing EmailMessage to support get_content and set_content with type-specific behaviour, email contentmanager raw_data_manager for the ContentManager instance that handles raw bytes and str payloads without any conversion, email contentmanager content_manager for the standard ContentManager instance used by email.policy.default that intelligently handles text plain text html multipart and binary content types, email contentmanager get_content_text for the handler that returns the decoded text payload of a text-star message part as a str, email contentmanager get_content_binary for the handler that returns the raw decoded bytes payload of a non-text message part, email contentmanager get_data_manager for the get-handler lookup used by EmailMessage get_content to find the right reader function for the content type, email contentmanager set_content text for the handler that creates and sets a text part correctly choosing charset and transfer encoding, email contentmanager set_content bytes for the handler that creates and sets a binary part with base64 encoding and optional filename Content-Disposition, email contentmanager EmailMessage get_content for the method that reads the message body using the registered content manager handlers, email contentmanager EmailMessage set_content for the method that sets the message body and MIME headers in one call, email contentmanager EmailMessage make_alternative make_mixed make_related for the methods that convert a simple message into a multipart container, email contentmanager EmailMessage add_attachment for the method that attaches a file or bytes to a multipart message, and email contentmanager integration with email.message and email.policy and email.mime and io for building high-level email readers attachment extractors text body accessors HTML readers and policy-aware MIME construction pipelines.

5 min read Feb 12, 2029
AI

Claude Code for email.charset: Python Email Charset Encoding

Control header and body encoding for international email with Python's email.charset module and Claude Code — email charset Charset for the class that wraps a character set name with the encoding rules for header encoding and body encoding describing how to encode text for that charset in email messages, email charset Charset header_encoding for the attribute specifying whether headers using this charset should use QP quoted-printable encoding BASE64 encoding or no encoding, email charset Charset body_encoding for the attribute specifying the Content-Transfer-Encoding to use for message bodies in this charset such as QP or BASE64, email charset Charset output_codec for the attribute giving the Python codec name used to encode the string to bytes for the wire format, email charset Charset input_codec for the attribute giving the Python codec name used to decode incoming bytes to str, email charset Charset get_output_charset for returning the output charset name, email charset Charset header_encode for encoding a header string using the charset's header_encoding method, email charset Charset body_encode for encoding body content using the charset's body_encoding, email charset Charset convert for converting a string from the input_codec to the output_codec, email charset add_charset for registering a new charset with custom encoding rules in the global charset registry, email charset add_alias for adding an alias name that maps to an existing registered charset, email charset add_codec for registering a codec name mapping for use by the charset machinery, and email charset integration with email.message and email.mime and email.policy and email.encoders for building international email senders non-ASCII header encoders Content-Transfer-Encoding selectors charset-aware message constructors and MIME encoding pipelines.

5 min read Feb 11, 2029
AI

Claude Code for email.utils: Python Email Address and Header Utilities

Parse and format RFC 2822 email addresses and dates with Python's email.utils module and Claude Code — email utils parseaddr for splitting a display-name plus angle-bracket address string into a realname and email address tuple, email utils formataddr for combining a realname and address string into a properly quoted RFC 2822 address with angle brackets, email utils getaddresses for parsing a list of raw address header strings each potentially containing multiple comma-separated addresses into a list of realname address tuples, email utils parsedate for parsing an RFC 2822 date string into a nine-tuple compatible with time.mktime, email utils parsedate_tz for parsing an RFC 2822 date string into a ten-tuple that includes the UTC offset timezone in seconds, email utils parsedate_to_datetime for parsing an RFC 2822 date string into an aware datetime object with timezone, email utils formatdate for formatting a POSIX timestamp or the current time as an RFC 2822 date string with optional usegmt and localtime flags, email utils format_datetime for formatting a datetime object as an RFC 2822 date string, email utils make_msgid for generating a globally unique Message-ID string with optional idstring and domain components, email utils decode_rfc2231 for decoding an RFC 2231 encoded parameter value into a tuple of charset language and value, email utils encode_rfc2231 for encoding a string as an RFC 2231 encoded parameter value, email utils collapse_rfc2231_value for collapsing a decoded RFC 2231 tuple to a Unicode string, and email utils integration with email.message and email.headerregistry and datetime and time for building address parsers date formatters message-id generators header extractors and RFC-compliant email construction utilities.

5 min read Feb 10, 2029

Put these ideas into practice

Claude Skills 360 gives you production-ready skills for everything in this article — and 2,350+ more. Start free or go all-in.

Back to Blog

Get 360 skills free