What do API Gateways and Reverse Proxies have in common?
They both manage incoming requests.
What’s the purpose of an API Gateways?
It serves as a single point of entry, typically in microservice architectures to manage and route requests to the appropriate services.
What are a few primary characteristics of an API Gateways? (Name 4)
They provide:
What is the purpose of a Reverse Proxy?
It’s a server proxy that retrieves resources for a client from one or more servers.
What are the primary characteristics of a Reverse Proxy? (Name 4)
They are:
- Load Balancing (distributes traffic across multiple services)
- Security (privacy by nature, server anonymity)
- Caching (cached content to reduce load)
- SSL Termination (SSL decryption instead of relying on each server to do that)
What’s a common use case for a Reverse Proxy?
A common single point for handling cross-cutting concerns for monolithic or microservice architectures like security, caching, etc.
How do API Gateways and Reverse Proxies differ in their roles?
API gateways focus on application-level traffic. Reverse proxies focus more on network or cross cutting concerns.
How do API Gateways and Reverse Proxies differ in terms of complexity?
API Gateways tend to be more complex or support more complicated features (request transformation, rate limiting, etc.).
Reverse proxies tend to be simpler as they focus on network-level objectives like efficiency and security (cross cutting concerns)
At a high level describe an API Gateway and Reverse Proxy (in terms of what they both do, and how they are different)
Both are components that manage traffic in a system. API gateways focus more on routing and orchestrating traffic to the appropriate sources whereas Reverse Proxies generally focus on high level/cross cutting concerns like efficiency.