Backend for frontend

/02 About

A dedicated backend per client experience (web, mobile) that shapes and aggregates calls to shared domain services.

Each client experience gets a thin backend owned by the team that builds the client. It aggregates and reshapes data from shared services so the client stays simple and fast. When to use: web and mobile clients with different needs, several downstream services per screen, and client teams that need to move without changing shared APIs. Trade-offs: clients get exactly what they need with fewer round trips; the cost is more deployables and the risk of duplicated logic. Keep business rules in the domain services, not the backends for frontend.

Published by Lattix · 9 elements · 11 relationships · validated on publish