Software → System Design
API Gateway
An entry point that routes, secures, and manages API traffic for backend services.
Motivation
API Gateway exists because teams need a practical way to solve a recurring problem in real systems. It gives engineers a shared abstraction for discussing trade-offs instead of treating every implementation as unique.
Where it fits
API Gateway belongs to the software track in the system design layer. It is useful when reasoning about nearby concepts such as Load Balancer, Microservices Architecture.
Mental model
Think of API Gateway as a named design pressure: it usually improves one quality, such as scalability, safety, usability, or operability, while adding constraints that must be understood.
Example in practice
When API Gateway appears in a system, the important question is not only what it is, but why the system needs it and what failure modes it introduces.
Common mistakes
- Using API Gateway because it is fashionable rather than because the problem requires it.
- Ignoring the operational cost or learning curve.
- Treating the concept as isolated instead of connecting it to neighboring concepts.