Backend for frontend

A dedicated API layer per client type, such as mobile and web, shaped for that client's screens. It avoids chatty clients and lets each team evolve its API independently.

Where it shows up in real systems

  • API gateway

    Centralises cross-cutting concerns so services stay simple. Validating JWTs locally costs almost nothing, while calling an auth service on every request adds latency and a dependency.

    In production: Amazon API Gateway, Kong, Apigee, Azure API Management, Tyk

See it break, then fix it

Build an architecture, send it a day of traffic and outages, and learn why it holds or fails. Free to start.

Open the learning path Open the sandbox