Api Gateway easy
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?
- A By automatically increasing the CPU and RAM capacity of the backend microservices.
- B By implementing 'Rate Limiting' (Throttling) to reject excessive requests before they reach the backend.
- C By encrypting the incoming traffic to make it harder to process.
- D By redirecting the malicious traffic to a secondary database for analysis.
Answer: B. By implementing 'Rate Limiting' (Throttling) to reject excessive requests before they reach the backend.
The Gateway acts as a shield. It tracks the number of requests per second for each client or IP. If a threshold is exceeded, it immediately returns a `429 Too Many Requests` status code, preventing the flood of traffic from overwhelming and crashing the internal services.
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'?
- 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?
- What is the primary operational benefit of performing 'SSL Termination' at the API Gateway?