Backend for Frontend
DistributedSpecialized backend for each type of client
Principles
One backend per client typeAdapts data to the clientReduces over-fetchingSpecific optimization
When to use
Multiple client types with different needs, platform-specific teams
When not to use
Single client type, generic API is sufficient
Pros and Cons
Ventajas
- + Optimized for each client
- + Less logic in frontend
- + Independent evolution
- + Better mobile performance
Desventajas
- - Possible logic duplication
- - More services to maintain
- - Coordination between BFFs