GRAPHQL VS. BFF: A Critical Perspective


50 minutes

Picture yourself working with an app that has a web and a mobile version, or better yet, just several different types of clients that consume the same APIs but are being built by totally different teams. The functionalities they provide are distinct, hence the need for distinct sets of data and functionalities.

You might think that the solution for this is having an “as generic as possible” backend for all UI’s. From my experience, this kind of backend leads to huge issues in matters of performance, entangled user experience as well as extra and unnecessary communication for the development teams to align and meet their needs.

Fortunately, there is a promising set of approaches taking the stage as they are created to optimize how front-end applications collaborate with backends: BFF (Backend-For-Frontend) pattern and GraphQL. Given these two approaches, which one is the right to consider?

Join me in a talk where we will discuss the two approaches, underline both their good and bad sides, and determine which you should consider as the most appropriate for your frontend application and business context.


Mihaela Roxana Ghidersa

Software Engineer at Strongbytes

Software developer and technology passionate- I enjoy building and delivering quality, all the while trying to have fun as much as possible. I am a perceptive and innovative individual that’s not afraid to exploit its best version and go the extra mile outside the comfort zone of conventional. This exact desire, of getting out of my comfort zone, led me in the last years to change the context from full-stack, frontend, API design to technical leadership and architecture.

Keep up to date with the latest news