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 provides every client with one consistent entrance, but the mobile team encounters problems after a year because its product screen needs data from six services