ApiGateway [pattern] v1.0.0

An API Gateway is a single ingress that fronts the microservice fleet. Clients (web, mobile, partner) talk to one URL; the gateway routes to internal services, fans out parallel calls, aggregates responses, terminates TLS, applies authn/authz, and rate-limits. It hides the internal service topology from external callers.

Label

API Gateway — single entry point fronting many services

Problem

A mobile client that talks to 20 microservices directly has to know all 20 hostnames, manage 20 connections, hold 20 auth tokens, and round-trip 20 times for one screen. The internal topology leaks to the client; refactoring services breaks every client.

Solution

    Insert a gateway between clients and services:

      Client → Gateway → [Service A, Service B, Service C, ...]

    Gateway responsibilities:
      - Routing: /users/* → user-service; /orders/* → order-service.
      - Aggregation: one client call fans out to multiple services in parallel; merged response.
      - Cross-cutting: TLS termination, auth, rate limiting, request logging.
      - Protocol translation: REST in, gRPC or AMQP out.

    Variants:
      - Backends-for-Frontends (BFF): one gateway per client type (web BFF, mobile BFF).
  

ApiGateway [pattern] v1.0.0

An API Gateway is a single ingress that fronts the microservice fleet. Clients (web, mobile, partner) talk to one URL; the gateway routes to internal services, fans out parallel calls, aggregates responses, terminates TLS, applies authn/authz, and rate-limits. It hides the internal service topology from external callers.

Label

API Gateway — single entry point fronting many services

Problem

A mobile client that talks to 20 microservices directly has to know all 20 hostnames, manage 20 connections, hold 20 auth tokens, and round-trip 20 times for one screen. The internal topology leaks to the client; refactoring services breaks every client.

Solution

    Insert a gateway between clients and services:

      Client → Gateway → [Service A, Service B, Service C, ...]

    Gateway responsibilities:
      - Routing: /users/* → user-service; /orders/* → order-service.
      - Aggregation: one client call fans out to multiple services in parallel; merged response.
      - Cross-cutting: TLS termination, auth, rate limiting, request logging.
      - Protocol translation: REST in, gRPC or AMQP out.

    Variants:
      - Backends-for-Frontends (BFF): one gateway per client type (web BFF, mobile BFF).
  

Relations

enhances: [@backend-architecture/pattern-service-registry]

Label

API Gateway — single entry point fronting many services

Problem

A mobile client that talks to 20 microservices directly has to know all 20 hostnames, manage 20 connections, hold 20 auth tokens, and round-trip 20 times for one screen. The internal topology leaks to the client; refactoring services breaks every client.

Solution

    Insert a gateway between clients and services:

      Client → Gateway → [Service A, Service B, Service C, ...]

    Gateway responsibilities:
      - Routing: /users/* → user-service; /orders/* → order-service.
      - Aggregation: one client call fans out to multiple services in parallel; merged response.
      - Cross-cutting: TLS termination, auth, rate limiting, request logging.
      - Protocol translation: REST in, gRPC or AMQP out.

    Variants:
      - Backends-for-Frontends (BFF): one gateway per client type (web BFF, mobile BFF).
  

Enhances

• @backend-architecture/pattern-service-registry