0Pricing
GraphQL APIs with Spring Boot · Pelajaran

Penyiapan dan Pengelolaan Gerbang

Konfigurasikan dan terapkan Apollo Gateway untuk menyusun serta mengekspos subgraf federasi Anda sebagai satu graf terpadu.

Penyiapan dan Pengelolaan Gerbang adalah pelajaran GraphQL APIs with Spring Boot gratis di CoddyKit. Ini adalah pelajaran 3 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar GraphQL APIs with Spring Boot, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus GraphQL APIs with Spring Boot mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

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.

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Penyiapan dan Pengelolaan Gerbang” gratis?

Ya — teks lengkap “Penyiapan dan Pengelolaan Gerbang” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus GraphQL APIs with Spring Boot, upgrade ke CoddyKit PRO. Kursus GraphQL APIs with Spring Boot mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Penyiapan dan Pengelolaan Gerbang”?

Konfigurasikan dan terapkan Apollo Gateway untuk menyusun serta mengekspos subgraf federasi Anda sebagai satu graf terpadu. Kamu berlatih GraphQL APIs with Spring Boot dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai GraphQL APIs with Spring Boot?

Tidak diperlukan pengalaman sebelumnya. GraphQL APIs with Spring Boot di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 3 dari 4.

Berapa lama pelajaran “Penyiapan dan Pengelolaan Gerbang” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran GraphQL APIs with Spring Boot ini?

Ya. Setiap pelajaran GraphQL APIs with Spring Boot menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

  1. Pengantar Apollo Federation
  2. Membangun Subgraf Federasi
  3. Penyiapan dan Pengelolaan Gerbang
  4. Referensi Entitas dan Direktif @key
← Kembali ke GraphQL APIs with Spring Boot