What problem does it solve?
Clients calling microservices directly leads to tight coupling, security sprawl, and complex client logic. An API gateway consolidates authentication, rate limiting, routing, and transformation at the edge — clients call one endpoint; the gateway handles the rest.
Core Features & Use Cases
- Edge gateway for central authentication, rate limiting, routing, and request/response transformation
- Backend-for-frontend (BFF) pattern: one gateway per client type (web, mobile, API)
- Health checks, monitoring, and circuit breakers for backend services
- CORS, request validation, and request logging to improve security and observability
- Use case: frontend apps needing access to multiple microservices through a single entry point with consistent security and response composition
Quick Start
Configure and deploy an edge API gateway to route to services, enforce authentication, and apply rate limits for frontend clients.