The BFF pattern has a specific architectural vocabulary. Practice the collocations for aggregating microservice data, shaping client-specific responses, avoiding tight coupling, and enforcing contracts in BFF architecture discussions.
0 / 5 completed
1 / 5
The mobile team requested a dedicated BFF to ___ data from three microservices into a single API response.
Aggregate data is the technical collocation for the primary function of a Backend for Frontend pattern. 'Merge' implies data unification at the record level; 'combine' is generic; 'collect' is too passive. 'Aggregate' is the precise API design term for combining results from multiple sources into one response.
2 / 5
The BFF layer was responsible for transforming the raw data into a ___ tailored to the mobile client's needs.
Shape tailored to the client is the natural API design collocation. In BFF discussions, 'shape' refers to the exact structure of the JSON response. 'Format' implies serialization type; 'structure' is less idiomatic in API contract language; 'response' is too broad. 'Shape' is the standard term in GraphQL and REST API design discourse.
3 / 5
Each client team maintained their own BFF to avoid ___ coupling between frontend requirements and shared API contracts.
Tight coupling is the canonical software architecture collocation. 'Strong coupling' is sometimes used but less standard; 'close coupling' is informal; 'rigid coupling' is not idiomatic. 'Tight coupling' vs 'loose coupling' is the standard terminology in software architecture and BFF pattern discussions.
4 / 5
The contract between the BFF and the iOS client was ___ through a shared TypeScript interface that both teams maintained.
Contract enforced through an interface is the natural collocation in API design language. 'Defined' says what the contract says; 'established' is when it is created; 'governed' is broader. 'Enforced' specifically means the interface mechanically guarantees the contract is honored — the key benefit of TypeScript-shared contracts.
5 / 5
When the product design changed, the frontend team updated their BFF without affecting any ___ services.
Upstream services is the precise architectural collocation for the microservices that the BFF calls. 'Backend services' is too generic; 'downstream' refers to consumers of the BFF; 'core services' is informal. 'Upstream services' correctly describes the data sources in the BFF architecture topology.