What Is an API Gateway?

An API gateway is a single entry point that sits in front of one or more backend services, handling cross-cutting concerns like authentication, rate limiting...

Published November 17, 2026

An API gateway is a single entry point that sits in front of your backend services, routing requests and handling cross-cutting concerns such as authentication, rate limiting, caching and logging.

The concept

Clients call one URL; the gateway forwards to the right microservice and can aggregate several responses. This keeps auth and throttling out of every service.

Examples: Kong, AWS API Gateway, Apigee and NGINX. The gateway must itself be highly available.

One front door

/api/*routeClientsweb, mobileAPI gatewayauth, limitsServicesusers, orders
Cross-cutting rules are applied in one place.

Practical examples

Route by path (Nginx style)

location /users/  { proxy_pass http://users:3000; }
location /orders/ { proxy_pass http://orders:3000; }

Rate limit at the edge

limit_req_zone $binary_remote_addr zone=api:10m rate=10r/s;
location /api/ { limit_req zone=api burst=20; }

Token check at the gateway

Verify JWT → add X-User-Id header → forward to service

Common mistakes

  • Putting business logic in the gateway.
  • Making it a single point of failure.
  • Not forwarding trace IDs.

Key takeaways

  • One entry point for many services.
  • Centralises auth, throttling, logging.
  • Keep it logic-light and redundant.

FAQ

Gateway vs reverse proxy?

A gateway is a reverse proxy with API-specific features like auth and quotas.

Do I need one?

Mostly for microservices or public APIs; a monolith rarely does.

More HTTP articles