How deeply does ASP.NET Core in Action, 3e cover backend-for-frontend pattern?

Explains the authentication and forwarding flow, but does not detail implementation configuration or backend endpoint code.

Backend-for-frontend pattern

As explained in ASP.NET Core in Action, 3e

Backend 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.

The Backend for Frontend (BFF) pattern places a traditional ASP.NET Core application between a SPA and its real APIs. It authenticates users, stores bearer tokens securely, issues an authentication cookie, and forwards authenticated requests. section 25.2

A typical request flow is:

The user authenticates through OpenID Connect at the ASP.NET Core backend. section 25.2
The backend stores the bearer tokens and gives the browser an authentication cookie instead. section 25.2
The SPA sends requests with the cookie; the backend exchanges it for the appropriate bearer token and forwards each request to the real API. section 25.2

SPA without browser-held bearer tokens

A Blazor WebAssembly, React, or Angular frontend calls its ASP.NET Core backend using the authentication cookie. The backend adds the bearer token when calling the protected API, so the browser never receives that token. section 25.2

How ASP.NET Core in Action, 3e covers it

liveBook manning.com

Read ASP.NET Core in Action, 3e 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

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

The Design of Web APIs, Second EditionA 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.

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 ASP.NET Core in Action, 3e. The section links point to the parts of the book it draws on.