How deeply does Secure APIs cover backend-for-frontend pattern?

Explains the pattern’s purpose and gateway role, but stops short of implementation code or detailed interface design.

Backend-for-frontend pattern

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

The backend-for-frontend pattern exposes client-specific backend interfaces instead of making each frontend understand every underlying service. An API gateway can implement this pattern by encapsulating backend complexity and presenting interfaces tailored to client needs. section 9.1

Without an intermediary, clients must discover and call multiple API endpoints themselves. That increases client responsibility and spreads authentication, authorization, inventory, monitoring, and hardening across separate entry points. section 9.1

E-commerce API boundary

An e-commerce backend may contain APIs deployed across serverless platforms, Kubernetes clusters, and dedicated servers. A gateway can expose a client-oriented interface while hiding those deployment details and underlying API locations. section 9.1

How Secure APIs covers it

liveBook manning.com

Read Secure APIs 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

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 sent through an application programming interface to obtain data or invoke an operation.

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