0Pricing
GraphQL APIs with Spring Boot · Lección

Configuración y gestión del Gateway

Configure y despliegue un Apollo Gateway para componer y exponer sus subgrafos federados como un único grafo unificado.

Configuración y gestión del Gateway es una lección gratuita de GraphQL APIs with Spring Boot en CoddyKit. Esta es la lección 3 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de GraphQL APIs with Spring Boot, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de GraphQL APIs with Spring Boot incluye 4 lecciones en total.

Partes de esta lección aún no han sido traducidas y se muestran en inglés.

Gateway: The Unified API

In GraphQL Federation, the Apollo Gateway acts as the central entry point for all client applications. Think of it as the brain that understands your entire supergraph.

It takes multiple independent GraphQL services (called subgraphs) and combines their schemas into one unified, client-facing schema.

Why a Gateway is Essential

With a microservices architecture, you might have many backend services, each with its own GraphQL API. Without a gateway, clients would need to know about and query each service individually.

  • Unified Endpoint: Clients interact with a single GraphQL API.
  • Schema Composition: The gateway automatically stitches together the schemas from all subgraphs.
  • Simplified Client Logic: Clients don't need to know which service owns which data.

How the Gateway Works

When a client sends a query to the gateway, here's what happens:

  1. The gateway receives the query.
  2. It analyzes the query against the composed supergraph schema.
  3. It breaks down the query into smaller parts, determining which subgraph owns which piece of data.
  4. It sends sub-queries to the relevant subgraphs.
  5. It then combines the results from these subgraphs into a single response for the client.

Gateway Implementations

While your subgraphs can be built with Spring Boot (or any other framework), the gateway itself is often implemented using Apollo's own tools.

The most common and robust implementation is the Apollo Server Gateway, which is a Node.js-based server designed specifically for federation. This lesson will focus on setting up this standard gateway.

Basic Gateway Setup (Node.js)

Let's set up a minimal Apollo Gateway. First, create a new Node.js project and install the necessary packages:

npm init -y
npm install @apollo/gateway apollo-server

Then, create an index.js file:

const { ApolloGateway, RemoteGraphQLDataSource } = require("@apollo/gateway");
const { ApolloServer } = require("apollo-server");

const gateway = new ApolloGateway({
  serviceList: [
    { name: "products", url: "http://localhost:4001/graphql" },
  ],
  buildService({ name, url }) {
    return new RemoteGraphQLDataSource({ url });
  },
});

const server = new ApolloServer({ gateway });

server.listen({
  port: process.env.PORT || 4000
}).then(({ url }) => {
  console.log(`🚀 Gateway ready at ${url}`);
});

Configuring Subgraphs

In the previous code, the serviceList array is crucial. It tells the gateway which subgraphs exist and where to find them. Each object in the array needs two properties:

  • name: A unique identifier for the subgraph (e.g., "products").
  • url: The endpoint where the subgraph's GraphQL API is running (e.g., "http://localhost:4001/graphql").

Adding More Subgraphs

As you develop more microservices with GraphQL APIs, you simply add them to the serviceList. The gateway will automatically compose their schemas into the unified graph.

Here's how you'd add a reviews subgraph running on port 4002:

const { ApolloGateway, RemoteGraphQLDataSource } = require("@apollo/gateway");
const { ApolloServer } = require("apollo-server");

const gateway = new ApolloGateway({
  serviceList: [
    { name: "products", url: "http://localhost:4001/graphql" },
    { name: "reviews", url: "http://localhost:4002/graphql" },
  ],
  buildService({ name, url }) {
    return new RemoteGraphQLDataSource({ url });
  },
});

const server = new ApolloServer({ gateway });

server.listen({
  port: process.env.PORT || 4000
}).then(({ url }) => {
  console.log(`🚀 Gateway ready at ${url}`);
});

Running and Accessing the Gateway

Once your index.js is set up, you can start the gateway:

node index.js

The console will output the URL where your gateway is running, typically http://localhost:4000/. Open this URL in your browser to access the GraphQL Playground or GraphiQL interface provided by Apollo Server.

Querying the Unified Graph

Clients will send their GraphQL queries directly to the gateway's URL. The gateway handles all the internal routing and data fetching from the subgraphs.

For example, a query combining data from both a products and reviews subgraph might look like this:

query GetProductDetails {
  product(id: "prod-1") {
    name
    price
    reviews {
      id
      rating
      comment
    }
  }
}

Gateway Management Tips

Beyond initial setup, managing your gateway involves several best practices:

  • Deployment: Deploy the gateway as a standalone service, often alongside your subgraphs.
  • Monitoring: Use tools to monitor its performance, error rates, and latency.
  • Scaling: The gateway can be scaled horizontally to handle increased client traffic.
  • Schema Changes: Ensure your gateway is configured to pick up schema updates from subgraphs reliably (e.g., via Apollo Studio or a local schema registry).

Quick Check: Gateway Role

You've learned about the Apollo Gateway and its role in federation.

Recap: Gateway Essentials

Congratulations! You've learned about the Apollo Gateway, a crucial component in GraphQL Federation. It provides a unified API endpoint for clients, seamlessly composing schemas from various subgraphs and routing queries effectively.

By configuring the serviceList, your gateway becomes the single source of truth for your entire supergraph, simplifying client interactions and enabling a robust microservices architecture.

Preguntas frecuentes

¿La lección «Configuración y gestión del Gateway» es gratis?

Sí — el texto completo de «Configuración y gestión del Gateway» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de GraphQL APIs with Spring Boot, actualiza a CoddyKit PRO. El curso de GraphQL APIs with Spring Boot incluye 4 lecciones en total.

¿Qué aprenderé en «Configuración y gestión del Gateway»?

Configure y despliegue un Apollo Gateway para componer y exponer sus subgrafos federados como un único grafo unificado. Practicas GraphQL APIs with Spring Boot con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.

¿Necesito experiencia previa para empezar GraphQL APIs with Spring Boot?

No se requiere experiencia previa. GraphQL APIs with Spring Boot en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 3 de 4.

¿Cuánto tiempo toma la lección «Configuración y gestión del Gateway»?

La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.

¿Puedo escribir y ejecutar código en esta lección de GraphQL APIs with Spring Boot?

Sí. Cada lección de GraphQL APIs with Spring Boot incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.

Todas las lecciones de este curso

  1. Introducción a Apollo Federation
  2. Construcción de subgrafos federados
  3. Configuración y gestión del Gateway
  4. Referencias de entidades y la directiva @key
← Volver a GraphQL APIs with Spring Boot