Why Backend for Frontend (BFF) pattern in Microservices? - Purpose & Use Cases

The Big Idea

What if your app could get exactly what it needs in one simple call, every time?

The Scenario

Imagine building a mobile app and a web app that both need data from many different services. Without a special approach, each app talks directly to all these services, juggling many requests and data formats.

The Problem

This direct approach is slow and confusing. Each app must handle many calls, combine data itself, and deal with different response styles. It leads to duplicated code, more bugs, and poor user experience.

The Solution

The Backend for Frontend (BFF) pattern creates a custom backend for each app type. This backend gathers and shapes data from many services into exactly what the app needs, making the app simpler and faster.

Before vs After

✗ Before

app calls service A, service B, service C separately and merges data on client

✓ After

app calls its BFF once, which fetches and combines data from services A, B, and C

What It Enables

BFF lets each frontend get just the right data in one call, improving speed, reducing complexity, and enabling better user experiences.

Real Life Example

A shopping website and its mobile app use separate BFFs. The website BFF returns detailed product info with images, while the mobile BFF sends a lighter version optimized for small screens and slow networks.

Key Takeaways

Direct calls from frontend to many services cause complexity and slow responses.

BFF creates a tailored backend for each frontend, simplifying data fetching.

This pattern improves performance, reduces bugs, and enhances user experience.