BFF (Back for frontend) Architecture

A brief introduction

Photo by Avel Chuklanov on Unsplash
BFF Architecture
  • Optimized APIs for the different front ends, including APIs that optimize the customer experience
  • The minimum logic for the BFF, with calls to the specific services of each front end (for example a service that only uses the mobile app or the web app)
  1. Separation of responsibilities by type of Front, allowing the development teams to be separated by “BFFs” and giving them a specific backend that enhances the solution of each channel
  2. Isolation of the business backend from the specificities of the front ends (security, call optimization, integrations…)
  3. It allows the combination of architectures (Microservices, serverless, Legacy System isolation, it combines very well with the use of legacy backends and their modernization and erosion starting with the front ends
  4. Different development speeds per BFF, being able to start with multiple combinations (several new frontends and a legacy backend) allowing separate teams
  1. Reusing and coordination of services, given that duplicate services will be produced with total security, both in the apis and in the backend services of each of the BFFs
  2. Select the correct level of granularity of BFF. For this reason is necessary analyze in your architecure design the number of BFF to build (eg it´s neccesary split a BBF from Android and other for IPhone or a unique BFF Backend)



Passionate and curious about technology. IT Architect and engineer

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store