How deeply does The Design of Web APIs, Second Edition cover backend-for-frontend pattern?

Explains aggregation, optimization, ownership, alternatives, and layering risks without detailing implementation internals.

Backend-for-frontend pattern

As explained in The Design of Web APIs, Second Edition

A backend-for-frontend is a consumer-specific backend API that aggregates and optimizes one or more underlying APIs for a particular frontend application or channel.

A backend-for-frontend (BFF) is an experience API that aggregates and optimizes business APIs for a specific consumer, such as a mobile application or website. The consumer team usually manages it, keeping consumer needs separate from system-level complexity. section 13.8

Adapting a banking API

A legacy banking application can send POST but not PATCH. A BFF can transform its POST-only request for transfer updates. Before adding a consumer-specific layer, compare broader solutions: PUT may replace PATCH, while X-HTTP-Method-Override can represent PATCH or DELETE through POST. section 14.2.1

Use the pattern deliberately:

Choose GraphQL when its specific capabilities provide value beyond a well-designed REST API over HTTP/2. section 14.8.2
Control layer boundaries and duplication; uncontrolled growth can make a distributed system inefficient, brittle, and difficult to maintain. section 13.8

How The Design of Web APIs, Second Edition covers it

Cover of The Design of Web APIs, Second Edition

liveBook manning.com

Read The Design of Web APIs, Second Edition on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Python Concurrency with asyncioA backend-for-frontend service is a service dedicated to making backend calls and aggregating responses for a particular type of frontend client.
liveBook manning.com

ASP.NET Core in Action, 3eBackend for Frontend is an architecture pattern that provides a dedicated backend for a particular frontend, handling authentication and translating or forwarding frontend requests to downstream APIs.
liveBook manning.com

Secure APIsThe backends-for-frontends pattern provides client-specific backend interfaces tailored to the needs of different frontend applications.

Compare how 4 books explain backend-for-frontend pattern →

Related concepts

design patternkind of · A design pattern is a reusable, general solution structure for a recurring software design problem in a particular context.
backendkind of · A backend is a software component or subsystem that provides underlying processing, data access, execution, or services to clients or other components, typically behind a user-facing interface.
API gatewayconfigures · An API gateway is an intermediary that provides an entry point for client requests to backend APIs or services and routes or otherwise mediates those requests.
api calluses · An API call is a programmatic request or invocation through an application programming interface to access data or invoke an operation.

This explainer was generated by Manning's knowledge graph from the text of The Design of Web APIs, Second Edition. The section links point to the parts of the book it draws on.