What is Backend for Frontend?
Turkish: BFF (Backend for Frontend)
A BFF creates a separate backend layer for web, mobile, or other interfaces, shaping API responses for each client.
What is Backend for Frontend?
Backend for Frontend (BFF) is an architectural pattern that creates a dedicated backend layer for each type of client. A web dashboard, mobile app, and kiosk screen may call the same core services, but they often need different response shapes, performance tradeoffs, and session behavior.
How Does It Work?
A BFF gathers data from multiple services, removes unnecessary fields, returns a client-friendly model, and may enforce session or device-specific rules. A mobile BFF may optimize for smaller payloads and unreliable connections, while an admin-panel BFF may expose richer filtering and table data.
The pattern prevents frontend clients from calling every microservice directly, but a poorly designed BFF can scatter business logic across too many layers.
Business Use
SaaS products, customer portals, and mobile apps with different screens can use BFFs to simplify the user experience. An API gateway mainly handles routing, security, and traffic control; a BFF shapes responses for a specific frontend. The distinction becomes especially visible in microservice architectures and systems that expose REST API endpoints.
Before adopting BFF, teams should clarify ownership, caching strategy, versioning, and where repeated business rules belong.
Related Terms
An API Gateway sits between clients and services to centralize routing, authentication, quotas, observability, and versioning.
MicroserviceMicroservice architecture designs a large application as small services that can be developed, deployed, and scaled independently.
REST APIA REST API designs web services around resources and HTTP methods, making integrations predictable across web and mobile systems.