Microservices API Gateway & Service Mesh Architecture Guide
Distributed Routing, Rate Limiting, Service Discovery, & Observability
1. API Gateway Pattern in Distributed Systems
An API Gateway serves as a centralized entry point for client applications accessing underlying microservice fleets.
It abstracts service topology, handles protocol translation, enforces rate limiting, and manages cross-cutting security
concerns.
• Dynamic Routing & Load Balancing: Evaluates incoming request paths and routes traffic dynamically to
healthy service instances using round-robin or least-connection algorithms.
• Rate Limiting & Throttling: Protects downstream microservices from traffic spikes using Token Bucket and
Leaky Bucket algorithms.
• Centralized Authentication: Validates OAuth2 / JWT tokens at the boundary to prevent unauthenticated
requests from penetrating the internal service network.
2. API Gateway vs. Service Mesh Comparison
Dimension API Gateway (North-South) Service Mesh (East-West)
Primary Focus External client to internal service traffic Inter-service pod-to-pod communication
Deployment Centralized cluster or distributed edge reverse Sidecar proxy container deployed per
Model proxy application pod
API monetization, billing, consumer key mTLS encryption, distributed tracing, circuit
Key Capabilities
management breaking
Kong, AWS API Gateway, Apigee, Envoy
Popular Tooling Istio, Linkerd, Consul Service Mesh
Gateway
Microservices API Gateway & Service Mesh Architecture Guide • Enterprise Technical Manual • Knowledge Exchange Edition
Page 1 of 1