What is the main risk of the BFF pattern?
Business logic leaks into the BFFs and gets duplicated across them. Authorization rules are the dangerous case: if three BFFs each implement them from raw service data, the copies drift and one eventually grants access it should not.
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 a Backend for Frontend?
- 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.