Distributed Systems · Editable reference architecture
Backend for frontend architecture
An editable backend for frontend architecture reference showing Web client → Web BFF → Catalog service. Tailor aggregation without duplicating business ownership.
Open & Edit in DrawArc (Free, No Login Required)Your changes stay in a separate draft on this browser. Download an editable project to keep a portable copy.

6 components · 6 connections · Open the editor to zoom, move nodes and edit source.
Architectural overview
Backend for frontend architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Web client and reaches Catalog service through Web BFF. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Tailor aggregation without duplicating business ownership.
The diagram contains 6 distinct components and 6 directed relationships. A separate path connects Mobile client → Mobile BFF → Catalog service. A separate path connects Web BFF → Account service. A separate path connects Mobile BFF → Account service. These arrows describe logical interactions; they do not establish authentication, network access, atomic transactions or delivery guarantees. Label the actual protocol, payload contract and owner when adapting the drawing to your system. Keep synchronous and asynchronous boundaries explicit so that a reviewer can identify where a request ends and a later operation begins.
Before implementing this architecture, define expected load, data classification, latency budgets and recovery objectives. Give Web BFF a bounded dependency timeout and a documented failure response. Assign ownership to any state or external service added during implementation. Validate the decision above against your workload instead of treating the presence of a component as proof of reliability. Open the editable canvas, replace generic labels with real deployment units, and document the decisions that differ from this reference.
The real-world problem
Design or explain backend for frontend architecture with explicit ownership and dependency paths. Tailor aggregation without duplicating business ownership.
Data flow
Connections from this diagram. Branches and control signals are not a single chronological sequence.
- Web client → Web BFF. Define the interaction contract and trace the resulting response or state change.
- Web BFF → Catalog service. Define the interaction contract and trace the resulting response or state change.
- Mobile client → Mobile BFF. Define the interaction contract and trace the resulting response or state change.
- Mobile BFF → Catalog service. Define the interaction contract and trace the resulting response or state change.
- Web BFF → Account service. Define the interaction contract and trace the resulting response or state change.
- Mobile BFF → Account service. Define the interaction contract and trace the resulting response or state change.
Security boundaries
- Authenticate callers at the boundary before Web BFF accepts protected work; authorize the specific operation rather than trusting network placement.
- Use separate service identities and least-privilege permissions for Web BFF, Catalog service, Mobile client. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
- Validate untrusted inputs and restrict administrative/configuration endpoints separately from the main flow.
Failure handling
Web BFF is unavailable or slow
Response: Apply bounded timeouts and controlled backoff only where retrying is safe. Return an explicit failure or durable acceptance; do not report success before required work is committed.
Verify: Interrupt Web BFF in an isolated test and measure errors, recovery and any repeated side effects.
A dependency repeats or drops a request
Response: Use operation identifiers and explicit acknowledgement/reconciliation where needed. Verify idempotency before enabling retries.
Verify: Exercise the failure path with representative records and verify both the visible response and the resulting state.
An invalid or incompatible input reaches Web BFF
Response: Validate the input contract before effects are committed. Preserve rejected input identifiers without exposing secrets, and document a safe replay or correction procedure.
Verify: Send malformed and older-version inputs through Web client and verify rejection, observability and unchanged valid state.
Trade-offs and alternatives
Tailor aggregation without duplicating business ownership.
- Benefit
- Makes the ownership and interaction boundaries visible for a focused design review.
- Cost
- The 6 illustrated components still require contracts, monitoring and operational ownership; extra boundaries can add latency and failure modes.
- Alternative
- Use a simpler deployment when it meets the same requirements, or split a boundary only after measuring a specific need.
Logical boundaries versus deployment units in Backend for frontend architecture
- Benefit
- Keeps the responsibilities of Web client, Web BFF, Catalog service visible without requiring a separate server for each box.
- Cost
- A logical view does not establish isolation, independent scaling or high availability; those require a separate deployment design and operational tests.
- Alternative
- Co-locate components in a simpler deployment first when ownership and workload requirements permit it.
When to use this architecture
- Explain backend for frontend architecture to engineers or stakeholders using a concrete visual flow.
- Review this decision before deployment: Tailor aggregation without duplicating business ownership.
- Adapt a starting diagram for your own requirements, then record and validate every changed boundary.
Key components
- Web client
- Web client participates in backend for frontend architecture. Web client → Web BFF. Define its contract, owner and access permissions in your implementation.
- Web BFF
- Web BFF participates in backend for frontend architecture. Web client → Web BFF; Web BFF → Catalog service; Web BFF → Account service. Define its contract, owner and access permissions in your implementation.
- Catalog service
- Catalog service participates in backend for frontend architecture. Web BFF → Catalog service; Mobile BFF → Catalog service. Define its contract, owner and access permissions in your implementation.
- Mobile client
- Mobile client participates in backend for frontend architecture. Mobile client → Mobile BFF. Define its contract, owner and access permissions in your implementation.
- Mobile BFF
- Mobile BFF participates in backend for frontend architecture. Mobile client → Mobile BFF; Mobile BFF → Catalog service; Mobile BFF → Account service. Define its contract, owner and access permissions in your implementation.
- Account service
- Account service participates in backend for frontend architecture. Web BFF → Account service; Mobile BFF → Account service. Define its contract, owner and access permissions in your implementation.
Questions about this template
What does this backend for frontend architecture diagram show?
It shows 6 components with the core flow Web client → Web BFF → Catalog service. Tailor aggregation without duplicating business ownership.
Can I edit this diagram without signing in?
Yes. Open the template in the browser-local canvas to change nodes, connections and source. AI generation and cloud account storage require sign-in.
Is this a complete production implementation?
No. It is an editable reference. Validate the security controls, dependency behavior, capacity and recovery plan against your own requirements before implementation.
Validate your implementation
Use the relevant platform documentation to verify service limits, supported features and configuration. This diagram is an original reference rather than a reproduction of a provider deployment.