Backend for Frontend

The Pattern

Give each client experience its own thin backend: owned by the client's team: that aggregates service calls and shapes responses for that client's screens. One kitchen (the services), different menus (a BFF per experience): because the dine-in table and the drive-through window shouldn't be forced to share one laminated card.

The gateway gave every client one uniform door: and a year later, the mobile team is quietly suffering behind it. Their product screen needs data from six services: six round trips on a cellular network at ~300 ms each