Note: The examples used below are highly simplified. I made it up for the sake of the article. Of course, you’ll want to be more sophisticated in your approach for a real-life business example.

The idea for the Backend-For-Frontend pattern came from the software engineers at SoundCloud. Phil Calçado (one of the creators) gave an architectural explanation of the pattern, so you can go give it a look here.

Why the BFF pattern?

Let’s use a case study.

Suppose you are building an application for a Real estate firm, which allows users to view properties for sale, and probably book appointments or something.


This article walks us through the advances in dynamic web development, and how we can improve the dynamic nature of our web apps.

So, before now, the web was just a bunch of static HTML pages. Send a request for a page, wait, get the content of the page — content already hand-typed by the web developer. Good old days.

It wasn’t long after until the need for dynamic pages became obvious (I wonder why 🙃 ), and developers sought a way to dynamically control the final content rendered to the client (which is the web browser).

I won’t bore…

Joshua Etim

PHP Developer. I build fun projects with Python/Javascript. Amateur Software Architect.

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