menu
Techniques

BFF - Backend for frontends

ARCHIVED BLIP
Please be aware that we have archived this blip and are no longer actively keeping the information updated. The current edition of the radar only features items that we feel are new or noteworthy.Understand more
TRIAL?

Valuable services support many variations in clients, such as mobile versus web and different forms of web interface. It’s tempting to design a single back-end API to support all clients with a reusable API. But client needs vary, as do constraints such as bandwidth for mobile devices versus the desire for lots of data on fast web connections. Consequently it’s often best to define different back-end services for each kind of front-end client. These back ends should be developed by teams aligned with each front end to ensure that each back end properly meets the needs of its client.

History for BFF - Backend for frontends

Apr 2016
Trial?

Valuable services support many variations in clients, such as mobile versus web and different forms of web interface. It’s tempting to design a single back-end API to support all clients with a reusable API. But client needs vary, as do constraints such as bandwidth for mobile devices versus the desire for lots of data on fast web connections. Consequently it’s often best to define different back-end services for each kind of front-end client. These back ends should be developed by teams aligned with each front end to ensure that each back end properly meets the needs of its client.

Nov 2015
Trial?
Learn more about our approach to assessing technology & build your own radar Get StartedNo thanks