Backend-for-Frontend (BFF) Pattern

When organizations transition to microservices, they frequently attempt to build a single universal API to serve all client applications (Desktop Web, iOS, Android, Smart TVs, Voice Assistants). This one-size-fits-all approach inevitably degrades across multiple dimensions:

1. Radically Different Network & Hardware Constraints:

• Desktop Web: High-speed broadband connections (1 Gbps) and massive 4K displays capable of rendering rich tabular dashboards with 50+ data columns.
• Mobile Phones: Fluctuating cellular networks (3G/4G/5G) with high latency and battery constraints. Every extra kilobyte of unused JSON slows down rendering and drains battery life.
• Smart TVs & IoT: Severely constrained CPU and memory. Complex JSON payload parsing causes UI stutter and frame drops.

2. Organizational Deadlock & Deployment Friction:

When the iOS team wants a new streamlined endpoint, while the Web team needs additional nested fields on the same endpoint, the backend team becomes a bottleneck. Changes must be debated, coordinated, and thoroughly regression-tested across all platforms, slowing down release velocity.