Api Gateway easy
What is the primary purpose of the 'Backend For Frontend' (BFF) pattern in API Gateway design?
- A To create a secondary copy of the entire backend database for faster read operations.
- B To provide specialized gateways for different client types (e.g., one for Mobile, one for Web) to tailor the data specifically for their needs.
- C To ensure that the frontend developers are allowed to write backend database queries directly.
- D To act as a version control system (like Git) for the API's source code.
Answer: B. To provide specialized gateways for different client types (e.g., one for Mobile, one for Web) to tailor the data specifically for their needs.
A web browser on a fast fiber connection can handle large data payloads. A mobile app on a spotty cellular connection cannot. The BFF pattern allows you to create a 'Mobile Gateway' that trims unnecessary fields and an 'IoT Gateway' that uses lightweight protocols, optimizing the experience for each client.
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?