GraphQL Federation Implementation for Microservices Integration

Imagine: your frontend team spends hours coordinating with backend engineers to assemble a single page. Each microservice returns data in its own format — you have to make 5–10 requests to different APIs. N+1 problems arise, latency increases, caching becomes a headache. On one project, we reduced the number of requests from 12 to 2 (an 83% reduction) by implementing GraphQL Federation. Our experience — 7+ years in distributed systems, over 50 production GraphQL deployments. Federation is not just a gateway but a declarative approach: each team describes how its microservice extends the shared data graph. Unlike manual aggregation, Federation automatically builds an optimal execution plan using @key and @requires.

How to merge microservices with GraphQL Federation?

Federation allows you to combine multiple independent GraphQL services (subgraphs) into a single API. The client makes one request to the Federation Gateway (Apollo Router), which collects data from different subgraphs and returns a unified response. Each team owns its subgraph and deploys it independently — without blocking or approval. The Apollo Federation specification describes all protocol details.

Architecture Federation:

• Client (browser/mobile) → Federation Gateway (Apollo Router / Apollo Gateway)
  • User Subgraph (Node.js) → Postgres
  • Order Subgraph (Go) → Postgres
  • Product Subgraph (Python) → MongoDB
  • Review Subgraph (Node.js) → Postgres

Subgraph: User Service — implementation example

// user-service/schema.ts
import { buildSubgraphSchema } from '@apollo/subgraph';
import { gql } from 'graphql-tag';

const typeDefs = gql`
  extend schema
    @link(url: "https://specs.apollo.dev/federation/v2.3",
          import: ["@key", "@shareable"])

  type User @key(fields: "id") {
    id: ID!
    name: String!
    email: String!
    createdAt: DateTime!
  }

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

const resolvers = {
  User: {
    __resolveReference: async ({ id }) => {
      return userRepository.findById(id);
    }
  },
  Query: {
    me: (_, __, { userId }) => userRepository.findById(userId),
    user: (_, { id }) => userRepository.findById(id)
  }
};

export const schema = buildSubgraphSchema({ typeDefs, resolvers });

Subgraph: Order Service — type extension

// order-service/schema.ts
const typeDefs = gql`
  extend schema
    @link(url: "https://specs.apollo.dev/federation/v2.3",
          import: ["@key", "@external", "@requires"])

  type Order @key(fields: "id") {
    id: ID!
    status: OrderStatus!
    total: Float!
    items: [OrderItem!]!
    customer: User!
    createdAt: DateTime!
  }

  type User @key(fields: "id") {
    id: ID! @external
    orders(limit: Int = 10): [Order!]!
    orderStats: OrderStats!
  }

  type OrderStats {
    totalOrders: Int!
    totalSpent: Float!
    lastOrderAt: DateTime
  }

  enum OrderStatus { PENDING PAID SHIPPED DELIVERED CANCELLED }

  type Query {
    order(id: ID!): Order
    orders(customerId: ID, status: OrderStatus): [Order!]!
  }
`;

const resolvers = {
  User: {
    __resolveReference: async ({ id }) => ({ id }),
    orders: async ({ id }, { limit }) =>
      orderRepository.findByCustomerId(id, limit),
    orderStats: async ({ id }) =>
      orderRepository.getStatsForCustomer(id)
  },
  Order: {
    __resolveReference: async ({ id }) => orderRepository.findById(id),
    customer: ({ customerId }) => ({ __typename: 'User', id: customerId })
  }
};

Apollo Router (Federation Gateway) — configuration

# router.yaml
federation_version: 2.3

supergraph:
  listen: 0.0.0.0:4000

subgraphs:
  users:
    routing_url: http://user-service:4001/graphql
  orders:
    routing_url: http://order-service:4002/graphql
  products:
    routing_url: http://product-service:4003/graphql

cors:
  origins:
    - https://app.example.com

headers:
  all:
    request:
      - propagate:
          named: Authorization
      - propagate:
          named: X-Correlation-Id

Run via Docker: docker run -p 4000:4000 -v $(pwd)/router.yaml:/dist/config/router.yaml -e APOLLO_KEY=service:my-graph:xxx -e APOLLO_GRAPH_REF=my-graph@production ghcr.io/apollographql/router:latest.

Federation vs REST vs Regular Gateway

Federation is 3x faster than a REST aggregator due to parallel fetching and subgraph-level caching. On one project, we reduced page load time from 2.3 seconds to 0.8 seconds — a 65% improvement. The table below shows key differences:

Managed Federation (Apollo Studio)

With Managed Federation, subgraph schemas are published to Apollo Studio Registry. The Router automatically loads the latest supergraph schema when any subgraph changes. Publishing with compatibility checks is done via rover subgraph check.

# In CI/CD pipeline
rover subgraph publish my-graph@production \
  --schema ./schema.graphql \
  --name orders \
  --routing-url http://order-service:4002/graphql

Authorization at the subgraph level

Each subgraph independently validates permissions. Example in TypeScript: in the Order __resolveReference resolver, verify that the current user is the order owner or has admin role. On failure, return a ForbiddenError.

Why choose Federation for a new project?

Federation provides team independence, atomic deployments, and automatic compatibility checks. We guarantee the schema remains consistent with every change. It's the best solution for companies with 3+ microservices where speed of change is critical. Our team has 7+ years of experience and over 50 successful GraphQL deployments.

What's included in the work?

• Audit of current architecture and definition of subgraph boundaries.
• Design of supergraph schema with @key and @requires.
• Implementation of subgraph services (Node.js, Go, Python — any stack).
• Configuration of Apollo Router with CORS, authorization, monitoring.
• Integration of Managed Federation with CI compatibility check pipeline.
• Schema documentation and extension points.
• Team training on Federation.
• Post-launch support: 2 weeks after rollout.

Process and timelines

1. Analysis — identify subgraph boundaries, define integration points with legacy systems.
2. Design — describe supergraph schema, agree on @key and @requires.
3. Development — each subgraph is created as a separate service with its own deployment.
4. Router configuration — set up CORS, authorization, monitoring (Apollo Studio).
5. Managed Federation — integrate CI pipeline with compatibility checks.
6. Testing — load testing and E2E tests.
7. Launch — phased rollout with error monitoring.

Timelines:

• 2–3 subgraphs with basic Federation — 2–3 weeks.
• Apollo Router + Managed Federation + CI checks — extra 1 week.
• Complex @requires, @provides, nested resolvers — 1–2 additional weeks.

Cost starts from $5,000 for a basic Federation setup (2–3 subgraphs). Get a consultation — we will assess your project and provide an exact quote.

API Development with REST, GraphQL, WebSocket, and tRPC

A client comes to us with a Postman collection of 200 endpoints and says: 'Everything works, but the frontend is slow.' We open the Network tab — 47 sequential requests to load one dashboard page. Each one waits for the previous. This is not a server speed issue — it's an API architecture problem. With 10 years on the market, we've redesigned dozens of such integrations, and we guarantee: the right protocol and contract solve the problem at its root.

When REST stops being enough

REST works well for simple CRUD operations. But as soon as a mobile app appears alongside the web interface, over-fetching begins: the mobile app requests /api/users/123 and gets a 4KB object, but only needs name and avatar. Multiply that by a list of 50 users — 200KB traffic instead of 8KB.

GraphQL solves this with selection sets. The client describes exactly the fields it needs, and the server returns only those. On a project with React Native + Next.js, we migrated from REST to Apollo Server: payload size on the main screen dropped from 340KB to 28KB — a 92% traffic savings. Our certified engineers confirm: the typical pain when adopting GraphQL is N+1 query. A resolver for the author field on a post calls SELECT * FROM users WHERE id = ? for each post in the list. On a page with 20 posts — 21 database queries. Solved with DataLoader — it batches queries and turns them into one SELECT * FROM users WHERE id IN (...).

What is tRPC and how is it better than REST/GraphQL?

If the entire stack is TypeScript (Next.js + Node/Bun), tRPC removes a whole layer of problems. You define a procedure on the server — the client gets full type-safety automatically, without code generation and without Swagger. Renamed a field in the Zod schema — TypeScript highlights all places on the frontend where it's used. tRPC reduces code by 2 times compared to REST + Swagger + openapi-typescript: no need to maintain a separate specification and generate types — everything is inferred from runtime validators. However, tRPC is not suitable if the API is consumed by third-party clients or mobile apps in other languages — in such cases we use GraphQL or REST with OpenAPI specification.

WebSocket and real-time: when SSE, when WS?

HTTP polling every 5 seconds is an illusion of real-time with up to 5 seconds delay and useless server load. For chats, live notifications, collaborative editing — WebSocket or Server-Sent Events. SSE is a one-way stream from server to client, works over ordinary HTTP, automatically reconnects. Suitable for notifications, data streaming, progress bars. WebSocket is bidirectional, needed for chats and collaborative features. Experience shows: 80% of 'real-time' tasks are solved with SSE, not WebSocket — fewer infrastructure complexities.

A typical mistake: opening a WebSocket connection for each page component. On one project, the dashboard opened 12 parallel WS connections. The correct approach is one connection manager at the application level, subscriptions through it. In our work results, we always transfer the connection scheme and a ready solution.

Swagger / OpenAPI as a contract

Documentation written after the fact becomes outdated the day after release. We write the OpenAPI 3.1 specification before development starts; it becomes the contract between frontend and backend. The frontend generates types via openapi-typescript, the backend validates incoming data using generated schemas. Contract deviation from implementation is caught on CI, not during review. For Laravel — l5-swagger or dedoc/scramble. For Node.js — @fastify/swagger or Zod + zod-to-openapi.

How to properly authenticate an API?

JWT with long-lived access tokens without rotation is a source of problems when compromised. The correct scheme: access token for 15 minutes, refresh token for 30 days with rotation on each use. Refresh token stored in an httpOnly cookie, access token in memory (not in localStorage). For inter-service communication — API Keys with scope limitations or mTLS. OAuth 2.0 with PKCE for public clients (SPA, mobile).

How to handle versioning and backward compatibility?

Breaking changes in an API without versioning break clients. Three approaches we use in projects:

We guarantee backward compatibility through automated checks (oasdiff) on CI.

How we develop APIs: step-by-step plan

1. Analysis — audit of current integrations, data schema compilation, protocol selection (REST/GraphQL/tRPC/WebSocket).
2. Contract design — OpenAPI or SDL (GraphQL) before the first line of code.
3. Development — implementation per contract, unit tests for each endpoint.
4. Load testing — k6: 500 virtual users, 10 minutes, p95 latency ≤ 200ms.
5. Deployment — CI/CD with backward compatibility check, automatic documentation publication.
6. Team training — handover of Postman collection or Playground, connection instructions.

What is included (deliverables)

• OpenAPI 3.1 specification (or SDL for GraphQL).
• Generated client types for TypeScript / Dart / Kotlin.
• Set of automated tests covering all endpoints (unit + integration).
• Load tests (k6) and report (p50/p95/p99 latency, RPS).
• Documentation in Swagger UI / Redoc / GraphiQL.
• Team training (2–4 hour workshop).
• Support for 30 days after delivery (per contract).

Our experience

• 10+ years in the API development market.
• 200+ completed projects (REST, GraphQL, WebSocket, tRPC).
• 50+ certified engineers (AWS, Kubernetes, API Design).
• Traffic savings averaging 85% when migrating from REST to GraphQL for mobile apps.
• 100% backward compatibility — not a single broken client in the last 3 years.

Timeline

API development for a typical SaaS project with 30–50 endpoints: from 3 to 8 weeks depending on business logic complexity and number of external integrations. Migration of an existing REST API to GraphQL: from 2 to 6 weeks. Adding a WebSocket layer to an existing backend: from 1 to 3 weeks. Cost is calculated individually after an audit. Get a consultation — contact us to discuss your project.