The Evolution of Frontend Development: From Monolithic Architecture to Serverless and BFF

As a frontend developer you may wonder what Node.js is for and why it is needed.

Since 2019 the buzzword “Serverless” has been everywhere, yet few truly know how to implement it.

Alibaba, a domestic leader in Node.js, introduced the BFF (Backend‑for‑Frontend) concept and later coined SFF (Serverless For Frontend), sharing insights from years of practice.

Evolution History

In the “ancient era” there was only design and development, with no distinction between front‑end and back‑end.

Web 1.0 relied on a centralized three‑tier MVC architecture (data access, service, web layers) using frameworks such as Struts, Spring, Hibernate and Dreamweaver.

The rise of distributed architectures introduced new challenges: scaling to massive traffic, higher performance demands, and tighter security requirements.

Consequently, frontend and backend roles diverged: frontend focused on design and UI implementation, while backend handled business modeling and system operations.

During the “stone age” the main pain point was the tight coupling between HTML delivered by frontend and templates rewritten by backend, making changes cumbersome.

Web 2.0 brought rich applications and frameworks (AJAX, jQuery, Angular, React, Vue), leading to front‑end/back‑end separation where backend provides APIs and frontend consumes them directly.

Micro‑service adoption further fragmented the backend, increasing API surface and performance overhead, prompting the introduction of an API aggregation layer.

Sam Newman’s Backends‑for‑Frontend (BFF) pattern emerged to give each UI team its own tailored backend, emphasizing service autonomy and “who uses it, who builds it”. Node.js was chosen as the optimal stack for BFF in many scenarios.

In large companies BFF adoption is smooth, while medium‑sized firms face cultural and infrastructural resistance.

Alibaba’s Ant Group has produced several efficiency‑boosting products: Basement (frontend workbench), Cloud Phoenix (visual site builder), DockerLab (lightweight DevOps), Egg (enterprise Node.js framework), and Ant Design (enterprise UI library).

Current challenges include talent shortage, heavy infrastructure processes, and resource waste due to low server utilization in BFF deployments.

The vision is to let pure frontend developers write a few functions to access backend capabilities, achieving scenario‑driven, low‑process, serverless, and automated operations.

Conclusion

Frontend development has evolved in a spiral manner, continuously revisiting past patterns with new technologies; the journey toward Serverless For Frontend is ongoing, and further sharing is expected.