The article explains why the backend team built three BFF services without serverless or GraphQL, basing the decision on business logic, team expertise, and organizational structure, and shows how the architecture aligns with different e‑commerce lines.
A tiny UI tweak that required a meeting with four backend groups exposed the pain of calling many micro‑services from the front‑end, and the article shows how introducing a Backend‑For‑Frontend (BFF) layer can aggregate, transform, and simplify those calls while improving reliability and performance.
A tiny front‑end tweak that required five microservice calls turned the front‑end into a glue layer, prompting a meeting with four backend teams, and the author explains how adopting a Backend‑for‑Frontend (BFF) pattern resolves such integration pain points with concrete examples and code.
This article analyses the ambiguous concepts of BFF in microservice architectures, distinguishing between “fat” BFFs that handle extensive orchestration and “skinny” BFFs that act mainly as transparent gateways, and discusses their responsibilities, advantages, drawbacks, and suitable scenarios.
This article examines the challenges of using Backend‑For‑Frontend (BFF) in product display scenarios, proposes a metadata‑driven GraphQL architecture that separates data fetching and presentation logic, details design patterns, performance optimizations, and the impact on development processes, and shares practical experiences from Meituan.
The article analyzes the massive, heterogeneous, and frequently changing information‑display features in Meituan's local‑service platform, proposes a standardized, component‑based, assembly‑oriented BFF architecture with series‑based function classification, pre‑assembly, and variability modeling, and reports over 50% efficiency gains and reduced interface complexity.
This article explains how to design microservice architectures by applying domain‑driven design, defining bounded contexts, using context mapping and event‑storming techniques, and addressing communication, consistency, and integration patterns such as event‑driven messaging and the Backend‑for‑Frontend approach.
This article explains the Backend‑for‑Frontend (BFF) pattern, comparing generic APIs with dedicated per‑UI backends, discussing when to adopt BFFs, handling multiple downstream services, reuse strategies, and their impact on team autonomy and mobile development.
