Portfolio ↗

Backend for Frontend

A narrow backend per client experience, owned by that client's team.

5Questions
12Flashcards
2Terms
Drill this topic All of Architecture Patterns
Questions

5 to work through

  1. intermediate

    A platform has a backend-for-frontend per client, and they have diverged with duplicated logic. Is BFF still the right pattern?

    2 min answer
  2. intermediate

    A product runs on web, iOS, Android and a television app. The shared API team is the bottleneck for every client change. Design the fix.

    3 min answer
  3. intermediate

    A quick-commerce platform serves a mobile app, a web app and a partner API from the same services. When does a backend-for-frontend earn its place?

    2 min answer
  4. intermediate

    A travel platform with Booking.com's catalogue breadth replaces nine client-side calls with one backend-for-frontend call that fans out to the same nine services. Mobile p99 improves by 40% on the first day. Each of the nine services holds 99.9% availability. What has the team given up, and when does the bill arrive?

    3 min answer
  5. intermediate

    Several client applications with different needs consume the same backend. When is a backend-for-frontend justified, and when does it become an unowned distributed monolith?

    2 min answer
Terminology

2 terms in this topic

pattern

Backend for Frontend

A dedicated backend per client experience, owned by the team that owns that client, so each surface gets exactly the payload it needs.

 pattern

Client-Specific Aggregation

A dedicated backend per client type that shapes and combines downstream data for that client's needs, owned by the client team.
Architecture Patterns

Neighbouring topics

Architecture Patterns

General material on architectural patterns and their trade-offs.

4 quiz 16 cards 12 terms

Layered Architecture

The default shape, its clarity, and where a technical partition fails.

4 quiz 11 cards 3 terms

Event-Driven Architecture

Publishing facts, and trading comprehensibility for decoupling.

4 quiz 12 cards 2 terms

Pipes and Filters

Independent transformation steps composed into a pipeline.

4 quiz 11 cards 3 terms

Publish/Subscribe

Broadcast to every subscriber, as distinct from work distribution.

6 quiz 13 cards 4 terms

Competing Consumers

Scaling throughput with instances, at the cost of ordering.

4 quiz 9 cards 4 terms

Saga

Local transactions with compensating actions across services.

5 quiz 7 cards 3 terms

CQRS

Separate models for writing and reading, each optimised for its job.

4 quiz 9 cards 3 terms

Event Sourcing

The event log as the system of record, with state as a projection.

4 quiz 5 cards 3 terms

Outbox

Making the event atomic with the business write it describes.

4 quiz 11 cards 4 terms

Strangler Fig

Incremental replacement behind a routing facade.

4 quiz 8 cards 3 terms

Anti-Corruption Layer

Translating a foreign model at the boundary so it does not leak in.

4 quiz 12 cards 2 terms

Sidecar & Ambassador

Cross-cutting behaviour in a co-deployed process.

3 quiz 8 cards 3 terms

Service Mesh

Sidecars applied estate-wide, and the scale at which that pays.

4 quiz 9 cards 3 terms

API Gateway

A single entry point for policy, routing and protocol translation.

4 quiz 13 cards 3 terms

Cell-Based Architecture

Complete isolated copies each serving a subset of customers.

5 quiz 10 cards 4 terms

Sharding Patterns

Directory versus embedded keys, logical shards and rebalancing.

3 quiz 12 cards 3 terms

Materialized Views

Precomputed query results, refreshed incrementally or in full.

4 quiz 10 cards 4 terms

Orchestration vs Choreography

A coordinator that knows the flow, or services that react to events.

5 quiz 11 cards 3 terms