0
0
Microservicessystem_design~12 mins

Popular gateways (Kong, AWS API Gateway, Nginx) in Microservices - Architecture Diagram

Choose your learning style9 modes available
System Overview - Popular gateways (Kong, AWS API Gateway, Nginx)

This system demonstrates how popular API gateways like Kong, AWS API Gateway, and Nginx manage incoming client requests to microservices. The gateways handle routing, security, and traffic control before forwarding requests to backend services.

Architecture Diagram
User
  |
  v
Load Balancer
  |
  v
API Gateway (Kong / AWS API Gateway / Nginx)
  |
  v
Microservices Cluster
  |
  v
Database
  |
  v
Cache
Components
User
client
Initiates requests to the system
Load Balancer
load_balancer
Distributes incoming traffic evenly to API gateways
API Gateway (Kong / AWS API Gateway / Nginx)
api_gateway
Manages routing, authentication, rate limiting, and request transformation
Microservices Cluster
service
Handles business logic and processes client requests
Database
database
Stores persistent data for microservices
Cache
cache
Speeds up data retrieval by storing frequently accessed data
Request Flow - 10 Hops
UserLoad Balancer
Load BalancerAPI Gateway (Kong / AWS API Gateway / Nginx)
API Gateway (Kong / AWS API Gateway / Nginx)Microservices Cluster
Microservices ClusterCache
CacheMicroservices Cluster
Microservices ClusterDatabase
DatabaseMicroservices Cluster
Microservices ClusterAPI Gateway (Kong / AWS API Gateway / Nginx)
API Gateway (Kong / AWS API Gateway / Nginx)Load Balancer
Load BalancerUser
Failure Scenario
Component Fails:API Gateway (Kong / AWS API Gateway / Nginx)
Impact:All incoming requests fail to route to microservices, causing service unavailability.
Mitigation:Deploy multiple API gateway instances behind the load balancer for redundancy and failover.
Architecture Quiz - 3 Questions
Test your understanding
Which component is responsible for routing and authentication of client requests?
AAPI Gateway (Kong / AWS API Gateway / Nginx)
BLoad Balancer
CCache
DDatabase
Design Principle
This architecture shows how API gateways act as a central point for managing client requests, providing security and routing before requests reach microservices. Load balancers ensure traffic is evenly distributed for scalability and availability. Caches improve performance by reducing database load.