liveBook · Manning

API gateway

As explained in Effective Platform Engineering

An API gateway is a service that receives API traffic and applies gateway functions such as routing, access management, and developer credential handling.

An API gateway receives API traffic and applies gateway functions such as routing, access management, and developer credential handling. section 7.1.3

For third-party API access, DNS can direct api.epetech.io to the gateway, which then forwards traffic to the actual API. section 7.1.3

Use an API gateway selectively:

  • Prefer it when third-party developers need a controlled external API entry point. section 7.1.3
  • Avoid adding it automatically to Kubernetes services when the Kubernetes API or service mesh already supplies the required capabilities. section 7.1.3
  • Account for additional traffic, configuration complexity, cost, and potential customer-support burden. section 7.1.3

External API traffic

An engineering platform exposes APIs at api.epetech.io. DNS points that subdomain to the API gateway, which redirects requests to the deployed API while supporting third-party access. section 7.1.3

How Effective Platform Engineering covers it

How deep it goes
Explains DNS-to-gateway routing and adoption trade-offs, but defers gateway implementation details.
Examples
Uses api.epetech.io, delegated hosted zones, and platform traffic paths as concrete infrastructure examples.
What it assumes
Assumes familiarity with APIs, DNS, Kubernetes services, and external developer access.
What you can do after
Evaluate when external API consumers justify a gateway instead of existing platform capabilities.
How it connects
Connects API gateways with DNS, Kubernetes API, service mesh, authentication, and authorization.

Also explained in

Compare how 6 books explain API gateway →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.