Ever heard of BFF? No, it's not about your Best Friend Forever; it stands for 'Backend for Frontend.' In a recent project at work, we stumbled upon a challenge during the migration of our legacy backend (let's call it project A) to microservices (B). Our e-commerce website, powered by Vue.js, was consuming APIs from project 'A.' However, as the migration unfolded, we found ourselves needing to call the same API from two different sources (project A and B) for distinct markets (e.g., Italy and Germany) that had different payloads.

Implementing the logic to transform payloads into the same response so that the existing Frontend doesn't break wasn't an issue, the real headache was maintaining and scaling it. This scenario is just one example of how things can get messy when dealing with business logic in a complex Frontend environment. To tackle this problem, we adopted the 'Backend for Frontend' pattern. This pattern allows us to keep business logic away from the Frontend while keeping it close.

In this session, I aim to explain BFF, exploring what it is, how it operates, and how to seamlessly integrate it into existing projects. I'll share insights from a case study, discussing both the advantages and disadvantages of adopting this approach.

Allow me to delve into the world of BFF and discover how it can revamp our approach to Frontend development.