Design
API Gateway
Design an API Gateway that handles routing, authentication, rate limiting, load balancing, and observability for microservices.
01 - Why interviewers ask this
It tests whether you know what belongs at the edge of a microservice architecture (auth, rate limiting, routing) versus inside individual services.
02 - Where this system exists in the real world
You interact with this design every day.
Kong / AWS API Gateway / Nginx-based gateways
Microservice architecture entry points
Third-party API monetization platforms
03 - What you'll master
Solve this once. Know it forever.
Centralize auth, rate limiting, and routing
Design request/response transformation logic
Reason about gateway high availability
04 - What you'll design
7 functional · 4 non-functional requirements.
Route incoming requests to the correct microservice based on path/method
6 more requirements inside
Sign in to unlock the full brief and start designing
05 - Companies that ask this
You may face this exact question in your next interview.
Ready?
Open the canvas.
Design it yourself.
See all requirements, use staged hints, run your code, and compare with community discussions - all on the same canvas.
Start Solving