Backend-for-Frontend

Shared backends force every frontend team to coordinate on every change. A BFF gives each team its own backend, cutting the dependency chain.

Overview

Backend-for-Frontend (BFF) means a stream-aligned team owns its frontend and a use-case-based backend tailored to their application’s or service’s needs. This decouples teams from shared backend platforms that force coordination on every change.

Without a BFF, frontend teams depend on a shared API that must serve every consumer. Changes require negotiation, versioning, and cross-team coordination.

With a BFF, each stream-aligned team owns the full vertical slice: the UI and the backend that serves it. The team can move independently, deploying changes without waiting on a shared service team. Shared platforms still exist, but the BFF insulates the stream-aligned team from their release cadence.

Resources

• Four Team Types — BFF enables stream-aligned team autonomy
• Contract Testing — used to maintain integration guarantees between teams with dependencies