Skip to content
Hallway
0:00 / 0:00

#bff#backendforfrontend#headlessarchitecture

What Is A Backend For A Frontend (BFF) Architecture Pattern

Going Headless with John

11K subscribers • 1 video on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by John Williams

Intermediate. Assumes working knowledge.

96K views4 years ago1 recommendation

Software designWeb developmentSoftware architectureDesign patternsAPI design

John Williams explains the Backend for Frontend architecture pattern and how it solves design gaps in headless applications.

Building applications using headless and MACH technologies require different architecture patterns, that goes beyond just the simple direct point to point pattern. So what is a backend for a frontend (BFF) architecture pattern, what does it solve and how does it fill a design gap in headless applications. See more of my articles on linked in linkedin.com/in/jjwilliams/ Most of what I have learned in the MACH / #HeadlessArchitecture world has been while building Amplience headless CMS, DAM and dynamic media services take a look at the Amplience Website and see a MACH platform in action amplience.com Introduction to what is a BFF problem of building headless Apps using point to point integration What is a BFF things to avoid and consider using the BFF architecture pattern

Why it's here

1 person recommends this

What people say. Recommended as a helpful explanation of the Backend-for-Frontend pattern in modern headless architectures.

u/heyshadowsmithin r/node • Recommends

On “BFF - Is a backend for frontend still necessary or even relevant nowadays?”

BFF is a pattern that appears in the MACH (Micro Services, API-first, Cloud Native, Headless) Architecture style. This is a relatively new style that is picking up steam. You can read all about it on machalliance.org. [Here’s a YouTube video that talks specifically about the Backend-for-Frontend pattern in MACH Architecture.] I hope this helps!
14View on Reddit