System Design Patterns: From Fundamentals to Real Systems
Vote

0% completed

​

Backend for Frontend

1. 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 set of services, a different API shape per client.

The gateway gave every client one uniform entrance: 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 about 300 ms each

.....

.....

.....

Like the course? Get enrolled and start learning!