Api Gateway easy
In a real-world building analogy, which of these roles best represents the function of an API Gateway?
- A A construction crew building the foundation of the house.
- B A family member living in one of the private rooms upstairs.
- C A Hotel Front Desk that greets guests, verifies their reservation (Auth), and tells them which elevator leads to their room (Routing).
- D A plumber who ensures the water flows through the pipes.
Answer: C. A Hotel Front Desk that greets guests, verifies their reservation (Auth), and tells them which elevator leads to their room (Routing).
The Gateway is the 'Receptionist' for your API. It handles the organizational 'overhead' tasks so the 'Rooms' (Microservices) don't have to worry about who is knocking or how they found the building. This keeps your architecture clean and organized.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Your Gateway communicates with backends via HTTP/1.1 connections. A slow backend service causes 'Head-of-Line Blocking'. How does switching to HTTP/2 as the Gateway-to-Backend transport mitigate this?
- What is the primary architectural role of an API Gateway in a microservices environment?
- Why is 'Stateless Token Validation' (e.g., using JWTs) significantly more scalable at the Gateway level than 'Stateful Validation' (e.g., using Opaque/Reference Tokens)?
- Your Gateway is configured to cache any URL ending in `.css` or `.jpg`. An attacker tricks a victim into visiting `https://api.com/v1/profile/info/style.css`. How can this lead to an 'Account Takeover'?
- An API is receiving a sudden surge of 10,000 requests per second from a single IP address. How does an API Gateway preserve the stability of the backend services?
- How can an API Gateway help prevent 'Double Charging' in a payment system when a mobile client retries a failed request due to a poor connection?