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.
Storing JWT tokens in localStorage has become a serious security risk because XSS attacks can steal them, so developers should adopt safer alternatives such as HttpOnly cookies, BFF‑backed sessions, or Service Worker‑based in‑memory storage, each with its own trade‑offs.
Storing JWT tokens in localStorage, once a common practice for front‑end authentication, now poses severe XSS risks; this article explains the vulnerabilities, compares HttpOnly cookies, BFF with cookies, and Service Worker‑based solutions, and recommends safer strategies for modern web applications.
This article analyzes the current bottlenecks of Bilibili's private messaging service, explains the technical challenges of massive data volume and traffic spikes, and presents a comprehensive multi‑layer architecture upgrade—including cache strategies, BFF refactoring, database sharding, and consistency mechanisms—to ensure scalability and reliability.
This article explains why storing JWT tokens in localStorage is unsafe due to XSS vulnerabilities, compares alternatives like HttpOnly cookies, BFF with cookies, and Service Workers, and offers guidance on choosing the most secure authentication strategy for modern frontend applications.
Storing JWT tokens in localStorage, once a common practice for front‑end authentication, now poses severe XSS risks, prompting developers to adopt more secure methods such as HttpOnly cookies with SameSite protection, BFF‑backed session cookies, or Service Worker‑based token handling, each with trade‑offs.
This article explains how treating JSON responses as UI components—by converting data models into view‑models on the server and exposing screen‑specific endpoints through a Backend‑for‑Frontend layer—solves the mismatch between REST resources and ever‑changing front‑end requirements.
This article explains how view‑driven (or BFF) API design replaces bulky data‑centric interfaces with UI‑aligned response models, reducing data redundancy, eliminating logic leakage, and streamlining front‑back collaboration for faster, more reliable product delivery.
The article outlines Ctrip Hotel's transition from a monolithic BFF model to a multi‑endpoint "one‑code‑many‑ends" architecture using NestJS, introduces a cloud‑function platform for improved performance and operational efficiency, and describes a dynamic gateway layer that further enhances front‑end flexibility across multiple client types.
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.
The article examines a large-scale supply‑chain system’s architecture, highlighting issues with service placement and dependencies, proposing an intermediate API layer for aggregation, distributed calls, and decoration, and ultimately recommending a Backend‑for‑Frontend approach to tailor APIs per client while reducing coupling.
This article explains how a complex supply‑chain platform with dozens of services and two client apps can be reorganized by introducing a gateway, an API aggregation layer, and a Backend‑for‑Frontend (BFF) pattern to reduce service coupling, simplify interface placement, and improve client‑specific adaptations.
This article analyzes common problems in a large‑scale supply‑chain backend—such as unclear service boundaries, tangled dependencies, and client‑specific adaptations—and proposes a layered solution using a dedicated API layer, BFF pattern, Spring Cloud components, and clear team division to improve modularity, reduce code duplication, and streamline development.
The article examines a complex supply‑chain system built on Spring Cloud, identifies issues with interface placement and tangled service dependencies, proposes an intermediate API layer and later a BFF pattern, and evaluates the trade‑offs, implementation details, and remaining challenges of these architectural changes.
Tango Flow is a low‑code workflow orchestration platform that unifies Cloud Music’s backend services—RPC, HTTP, FaaS and tool‑domain APIs—into visual, versioned workflows, offering drag‑and‑drop design, debugging, mock testing, multi‑tenant clustering, monitoring and continuous release to replace BFFs and accelerate full‑chain development.
This article examines the challenges of a complex supply‑chain system built on Spring Cloud, proposes introducing an API layer to handle aggregation, distributed calls and decoration, and further adopts a Backend‑for‑Frontend (BFF) approach to reduce service coupling, improve client‑specific optimization, and streamline team responsibilities.
This article explains the motivation behind Backend‑for‑Frontend, compares naive and decoupled BFF implementation patterns, evaluates RESTful, GraphQL and RPC options, and presents a TypeScript‑centric RPC‑BFF solution with schema‑driven validation, type inference, introspection, code generation and advanced optimizations such as merge, batch, streaming, caching and deduplication.
This article explains why BFF is needed in modern microservice architectures, describes thin and thick BFF designs, outlines typical inter‑process microservice structures, enumerates common BFF problems, and proposes governance principles to keep BFF focused on front‑end experience and backend orchestration.
This article examines the challenges of a complex supply‑chain system built on Spring Cloud, proposes an API aggregation layer and a Backend‑for‑Frontend (BFF) pattern to reduce service coupling and client‑specific adaptation, and discusses practical implementation details and team organization.
The article describes how Bilibili tackled exploding fan‑out reads on its video detail page by introducing a Redis‑backed business‑association index and a generic Data Aggregation Gateway, which together cut downstream service traffic and load by over 90% while simplifying aggregation across multiple terminals and scenarios.
This article shares a step‑by‑step experience of refactoring a finance‑BFF aggregation service from tightly coupled synchronous calls to a loosely coupled, fully asynchronous architecture, covering problem background, redesign goals, implementation details, Hystrix integration, monitoring, and practical usage examples.
This article presents a comprehensive overview of component-based development at ZhaiZhai, detailing the background, current challenges, the component model, classification, design, deployment process, performance gains, supporting ecosystem, and concluding insights, all supported by references and practical examples.
The article shares a chief architect’s experience designing a hybrid “big waterfall + small agile” delivery approach, microservice architecture, BFF layer, and team organization principles such as Conway’s law to address application boundary challenges in a massive state‑owned enterprise project.
The article shares a chief architect's experience on combining a large‑scale waterfall approach with agile iterations, detailing microservice and BFF design, team organization aligned with Conway's law, and practical application‑boundary principles for a distributed enterprise system.
The article explains how the Backend for Frontend (BFF) pattern creates dedicated, lightweight server‑side APIs for each UI type—desktop web, mobile, or third‑party—allowing teams to tailor functionality, reduce coupling, aggregate micro‑service calls, and improve autonomy while addressing performance, scaling, and organizational concerns.
This article explains how NetEase Cloud Music tackled the tight coupling between frontend UI and backend services by introducing a Backend‑For‑Frontend layer built on GraphQL, detailing the architectural choices, low‑code editor, custom directives, deployment pipeline, and the resulting improvements in scalability and developer productivity.
The article uncovers a lock‑induced latency in Retrofit’s service‑method cache during cold‑start, demonstrates how moving the synchronization to a class‑level lock and customizing Retrofit.create eliminates the bottleneck, and then shows how dynamic‑proxy hooks combined with Kotlin coroutines can add transparent caching and low‑intrusion BFF aggregation without altering the library.
This article describes the background, design decisions, architecture, core concepts (Serverless, BFF, FAAS), implementation details, performance results, and future plans of the internally built Seras platform that enables front‑end teams to write cloud functions without managing servers, improving code reuse, traceability, and deployment speed.
The article examines the challenges of interface placement, service dependencies, and client-specific adaptations in a complex supply‑chain system and proposes an API aggregation layer and Backend‑for‑Frontend (BFF) pattern, detailing implementation with Spring Cloud and practical team division.
This article presents a comprehensive micro‑frontend solution for H5 e‑commerce sites, covering background analysis, problem identification, architectural design with BFF layer, code examples for registration, routing, and progressive migration, and concludes with the benefits of modular, SEO‑friendly front‑end development.
This article describes how Baidu's commercial frontend team improved front‑end and back‑end collaboration efficiency by introducing a BFF layer, data‑direct capabilities, staged data tiering, and fragment‑based batch editing, ultimately reducing delivery time by over 50% while maintaining quality.
The article describes how Baidu's commercial front‑end team introduced a data‑direct capability and BFF layer to streamline front‑end/back‑end cooperation, reduce environment‑maintenance overhead, enable parallel development, and improve overall delivery efficiency across multiple project phases.
Baidu’s commercial front‑end team integrated an interface platform with a data‑direct capability—leveraging BFF layers, Redis‑based offline data injection, stub services, data grading, and fragment‑based batch editing—to enable true parallel front‑back end development, eliminate separate test environments, and cut average project delivery time by more than half across thousands of projects.
The article examines the difficulties encountered when implementing a Backend‑For‑Frontend (BFF) layer in the JD Finance app, introduces a visual service‑orchestration platform that replaces hard‑coded solutions with drag‑and‑drop workflows, details its core functions, architecture, and performance benefits, and demonstrates how it dramatically improves delivery speed, service governance, and debugging efficiency.
This article shares Ctrip's experience building GraphQL‑based Backend‑for‑Frontend services, covering the technology stack, data‑graph modeling, error handling with union types, non‑null field usage, performance optimizations, engineering practices such as data‑loader batching, virtual paths, monitoring, and testing.
This article explores Ant Group's front‑end R&D system, the challenges of large‑scale financial applications, and how a serverless, low‑code platform with BFF, function‑level deployment, and documentation‑as‑code practices can boost efficiency, safety, and scalability.
This talk explains Ant Group’s serverless‑based front‑end platform, detailing the current front‑end architecture, challenges of large‑scale financial services, and three core efficiency ideas—document‑as‑code, function‑level deployment, and integrated plugin capabilities—to streamline development and ensure safe production.
This article chronicles Bilibili’s transition from a PHP monolith to a Go‑based bilizone monolith, its subsequent decomposition into microservices, the adoption of Backend‑for‑Frontend (BFF) layers, and the eventual consolidation into a unified API gateway that streamlines routing, security, and traffic management across the platform.
This article examines how Service Mesh and API Gateway differ in responsibilities, explores the east‑west versus north‑south traffic concepts, discusses two implementation philosophies, and traces the evolving integration of sidecars, BFF, and unified gateway solutions in modern microservice architectures.
This article examines how Service Mesh and API Gateway differ in function and deployment, explores the philosophical debate over east‑west versus north‑south traffic when a gateway accesses internal services, and traces the evolving integration of sidecars, BFF layers, and cloud‑native architectures.
Front‑end development has progressed from early back‑end‑only sites to a distinct discipline covering HTML, CSS, and JavaScript, embracing SPA techniques, micro‑frontend architectures, and full‑stack capabilities via Node.js and BFF layers, requiring engineers to grasp both client presentation and server‑side concepts for collaborative, modular, reusable web applications.
This article explains how front‑end engineers can shift their mindset, adopt a BFF layer and GraphQL, and automate the integration with a data warehouse to become data owners, improve efficiency, and reduce reliance on back‑end resources in large‑scale data platforms.
This article examines the distinct responsibilities of Service Mesh and API Gateway, explores the philosophical debate over internal traffic classification, and details emerging integration patterns such as sidecar‑based gateways and BFF‑driven architectures, illustrated with real‑world examples from Ant Financial.
The article explains how a Backend‑For‑Frontend (BFF) layer can be constructed using GraphQL for on‑demand data fetching, JSON template engines for data transformation, and routing capabilities for version handling, resulting in a scalable, maintainable architecture that integrates with low‑code front‑end platforms.
This article explores how serverless infrastructure lets front‑end engineers combine front‑end and back‑end development through patterns like front‑end/back‑end separation, BFF, and integrated frameworks, offering lower costs, higher reliability, and faster iteration for modern web applications.
The talk explains how traditional Backend‑for‑Frontend (BFF) architectures, burdened by high costs and slow releases, evolve into a Serverless For Frontend (SFF) model that uses lightweight Node.js functions, VM2 isolation, and CGroup resource control to enable rapid, cost‑effective deployments and improved team efficiency.
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.
This article explains why and when to split existing microservices, validates the split idea with event storming and data‑model analysis, outlines guiding principles, and provides a detailed, step‑by‑step process—including code restructuring, testing, dependency removal, and database separation—to ensure a smooth transition.
This article recounts a team's evolution from traditional IaaS‑based front‑back separation to a micro‑frontend BFF model, detailing how they adopted OpenFaaS on Kubernetes to build serverless function services, covering deployment steps, code examples, underlying architecture, and auto‑scaling mechanisms.
The article describes a backend‑for‑frontend architecture that pushes GraphQL into the BFF layer, separates fetch and display units, drives execution with metadata, unifies query models, applies caching and parallel processing optimizations, and demonstrates over 50 % logic reuse and doubled development efficiency in production.
This article introduces six essential cloud‑native design patterns—Circuit Breaker, CQRS, Event Sourcing, Sidecar, BFF, and Strangler—explaining their purpose, implementation tips, and when to apply or avoid them to build scalable, resilient, and maintainable enterprise systems.
iQIYI created a GraphQL‑based Backend‑for‑Frontend layer that functions as a low‑code API generation platform—leveraging graphql‑java, REST integration, Prometheus monitoring, Velocity‑driven schema templates, and a visual console—to streamline micro‑service aggregation, cut duplicate development, accelerate front‑end delivery, and outline future scaling and migration challenges.
The article explains common development models, detailing the steps from requirement gathering to delivery, compares half‑separation and full separation of frontend and backend, outlines their advantages and disadvantages, and reflects on architectural responsibilities in line with Conway's Law.
Vivo Mall transformed its Java‑centric frontend into a layered Vue‑Node architecture, separating frontend and backend, unifying multiple platforms with BFF and SSR, building a shared UI library, adopting extreme modularization, and enforcing coding standards and quality tools to double development efficiency and improve scalability.
The article explains microservice fundamentals, the challenges of client‑to‑service communication, and how API gateways, Backend‑for‑Frontend patterns, and Service Meshes address these issues while outlining key gateway features, popular implementations, and selection criteria for robust backend architectures.
This article examines the evolving relationship between Service Mesh and API Gateway, clarifying their original responsibilities, discussing traffic direction semantics, and detailing how sidecar integration, BFF layers, and real‑world Ant Financial practices are driving a convergence toward more decentralized, cloud‑native API management.
This article explores how Serverless computing reshapes front‑end development by tracing the evolution of front‑end architectures, introducing Serverless concepts and services, presenting practical frameworks, CLI tools, and code examples, and offering best‑practice guidance on testing, performance optimization, and deployment patterns for modern web and mini‑program applications.
This article explores the evolution of ICBU’s cross‑border supply‑chain web architecture, detailing the rise of Serverless, the shift from traditional Webx to BFF and Egg‑based micro‑applications, the implementation of FaaS/EaaS, engineering and monitoring practices, and the resulting performance and business benefits.
NGW (Node Gateway) is a Node.js‑based frontend access layer that sits between a unified gateway and business services, providing dynamic request routing, Redis‑driven configuration, a Tapable plugin system, and containerized CI/CD to enable serverless BFF/SFF architectures with rapid builds, high reliability, and dramatically reduced deployment effort across multiple Tencent Cloud projects.
Facing tangled microservice calls and heavy front‑end data stitching, Fangdd’s engineering team evolved from monolithic PHP to a multi‑layered microservice architecture, introducing Duo‑GraphQL to unify data via GraphQL providers, a BFF layer, and optimized engine, dramatically improving development speed and performance.
This article traces the historical evolution of frontend development—from early monolithic web architectures through the rise of distributed systems and front‑end/back‑end separation, to modern serverless and Backend‑for‑Frontend (BFF) approaches—highlighting the shifting roles, challenges, and emerging solutions in the industry.
This article examines why GraphQL naturally emerges for complex front‑end data needs, details its language design, architecture, resolver middleware, mocking strategies, and various deployment patterns such as API‑gateway and BFF, offering practical guidance for building scalable GraphQL services.
This article explains serverless concepts for front‑end developers, outlines its evolution, benefits, and architecture—including BFF layers and SSR—then demonstrates a complete vocabulary mini‑program built with cloud functions, storage, monitoring, debugging, testing, deployment, and operational best practices.
The article shares Wang Baoping’s (Yu Bo) reflections on the essence of frontend technology, the rise of BFF architecture, the convergence with mobile, IoT and experience tech, and outlines future directions such as TWA, UI intelligence, data visualization, and natural‑virtual interaction.
The article reflects on the evolution of front‑end technology from early HTML/CSS/JS to Node‑based BFF architectures, discusses the convergence of front‑end with mobile, IoT and design, and outlines future directions such as TWA, UI intelligence, data visualization, and immersive experience technology.
The Guangzhou Node.js meetup recap covers practical uses of Thrift for cross‑language communication, the evolution of Node.js data APIs toward a BFF architecture, a concise introduction to TypeScript benefits, and innovative direct‑rendering techniques, all illustrated with speaker insights and event photos.
The article explores the rise of experience APIs and Backends for Frontends, discussing how microservice architectures, API facades, custom payloads, media types, Prefer headers, and GraphQL can be used to tailor APIs for diverse client platforms while weighing the trade‑offs for small versus large teams.
