What is a Backend for Frontend?
A dedicated backend gateway for one kind of client, such as mobile, web or partner API. It shapes responses to that client's needs and handles edge concerns like authentication, rate limiting and caching, so other clients are not forced into one compromise API.
Answered in
Backends for Frontends, and What Comes After: Value-Added Services and Domain GatewaysBFFs fix client sprawl, then duplicate authorization logic across themselves. The three-layer fix: edge, value-added services, and per-domain gateways.
Read the full analysisOther questions this article answers
More system design & architecture questions
- What is the main risk of the BFF pattern?
- What is a value-added service layer?
- What does a field mask do in an API?
- What is a cold cache problem?
- How does change data capture keep a cache correct?
- Why use add instead of set when warming a cache?
- Why partition the cache differently from the database?
- Why must a chat system store a message before confirming it?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.