BFF (Backend for Frontend)

Normal Behavior

An architectural pattern where a separate backend service is created for each specific frontend interface.

Failure Behavior

May drop requests or fallback to degraded mode under load.

Business Consequence

When a Backend-for-Frontend (BFF) layer goes down, the specific client interface it serves—such as an iOS mobile app or a React web dashboard—is entirely severed from the underlying microservice ecosystem. This tight coupling means that while the core backend might be perfectly healthy, the business still suffers a complete loss of revenue on that specific platform, forcing users to experience hard application crashes and unhandled state exceptions.

Visual Manifestation

"The mobile app or single-page application spins endlessly on a loading skeleton before crashing to a blank white screen, while the network tab in the browser's developer tools turns bright red with a cascade of HTTP 504 Gateway Timeout or CORS (Cross-Origin Resource Sharing) policy violations."

Satirical Behavior

"A bespoke middleware service invented so frontend developers can write server-side code without learning the core backend language, inevitably becoming a fragile, monolithic god-object that aggregates data slower than if the client just made three separate API calls."

Technical Terminology

Failure Indicators