Backend for Frontend (BFF) pattern in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Backend for Frontend (BFF) Pattern

What is the main purpose of using a Backend for Frontend (BFF) pattern in a microservices architecture?

A To provide a dedicated backend tailored to the needs of each frontend client, improving performance and user experience

B To create a single backend service that handles all frontend requests without customization

C To replace all microservices with one monolithic backend for simplicity

D To directly expose all microservices to the frontend without any intermediate layer

💡 Hint

Think about how different frontend clients might have different data needs and how BFF helps with that.

The BFF pattern creates a backend layer customized for each frontend client (like web, mobile). This helps optimize data fetching and reduces complexity on the frontend.

❓ Architecture

intermediate

Request Flow in BFF Pattern

In a system using the BFF pattern, which sequence correctly describes the flow of a user request from frontend to data retrieval?

A Frontend → Database → Microservices → BFF

B Frontend → Microservices → BFF → Database

C Frontend → BFF → Microservices → Database

D Frontend → Database → BFF → Microservices

💡 Hint

Remember that BFF acts as a middle layer between frontend and microservices.

The frontend sends requests to the BFF, which then calls the relevant microservices to gather data before responding.

❓ scaling

advanced

Scaling Challenges with Multiple BFFs

What is a common scaling challenge when implementing multiple BFFs for different frontend clients?

A All BFFs share the same database connection pool, causing contention

B Duplicated logic across BFFs increases maintenance overhead and resource usage

C BFFs cannot cache data, leading to excessive database load

D BFFs force frontend clients to handle complex data aggregation

💡 Hint

Think about how having separate backends for each frontend might affect code reuse and maintenance.

Multiple BFFs often duplicate similar logic tailored for each frontend, which can increase maintenance effort and resource consumption.

❓ tradeoff

advanced

Tradeoff of Using BFF Pattern

Which of the following is a key tradeoff when adopting the BFF pattern?

A Simplifies frontend development but increases backend complexity and deployment overhead

B Reduces backend complexity but requires frontend to handle all data aggregation

C Eliminates the need for microservices by consolidating all logic in BFF

D Removes the need for API gateways by exposing microservices directly

💡 Hint

Consider how adding a new backend layer affects system complexity and deployment.

BFF simplifies frontend work by tailoring APIs but adds complexity in backend management and deployment of multiple BFF services.

❓ estimation

expert

Capacity Planning for BFF Layer

You have a mobile app with 1 million daily active users and a web app with 500,000 daily active users. Both use separate BFFs. If the average request rate per user is 10 requests per hour during peak 4 hours, estimate the total peak requests per second the BFF layer must handle combined.

A Approximately 20,833 requests per second

B Approximately 6,250 requests per second

C Approximately 10,417 requests per second

D Approximately 4,167 requests per second

💡 Hint

Calculate total requests during peak hours, then convert to requests per second.

Total users = 1,000,000 + 500,000 = 1,500,000
Requests per user per hour = 10
Peak hours = 4
Total requests = 1,500,000 * 10 * 4 = 60,000,000
Seconds in 4 hours = 4 * 3600 = 14,400
Requests per second = 60,000,000 / 14,400 ≈ 4,167