Backend for Frontend

1. The Pattern

Give each client experience its own thin backend, owned by the client's team. It aggregates service calls and shapes responses for that client's screens. One set of services, a different API shape per client.

The gateway gave every client one uniform entrance. A year later, the mobile team is quietly suffering behind it. Their product screen needs data from six services. That is six round trips on a cellular network, at about 300 ms each. The responses carry 40 fields each, and the phone displays six