Practical Experience of FaaS Adoption in Alibaba's Big‑Taobao Industry

Background

This article shares the experience of the Big‑Taobao industry team in converting their services to Function‑as‑a‑Service (FaaS). It answers the three questions of Why, What and How, providing practical guidance for engineers interested in serverless adoption.

Business Background

Since 2019 the team has been the pioneer of FaaS within the group, applying it to scenarios such as iFashion and Tmall Sports. The goal is to move the data‑assembly logic from the BFF layer to the front‑end, turning front‑end developers into business partners.

Industry Characteristics

Most data capabilities already exist in the middle‑platform; the front‑end only needs to compose them. This “heavy orchestration, light data assets” model makes the front‑end a natural place for FaaS, reducing hand‑off cost and allowing deeper business insight.

Production Relationship Change

Traditional front‑back separation creates unclear boundaries and high integration cost. By letting the front‑end own the orchestration and sinking the back‑end to the middle‑platform, the team achieves a win‑win for front‑end, back‑end and product.

FaaS Progress and Benefits

More than ten lightweight applications have been fully FaaS‑ified. Front‑end engineers have evolved from page builders to business partners, gaining ownership of logic and contributing to product growth.

Value Dimensions

Empowering Front‑end : expands responsibility, lets engineers own business outcomes.

Improving Development Efficiency : a single front‑end developer can deliver a feature without a back‑end counterpart.

Becoming Business Partners : front‑end can directly influence revenue‑related metrics.

How to Judge Suitability

Two aspects: cost and benefit. Cost includes manpower and technical difficulty (e.g., complex DB, high‑concurrency tasks). Benefit includes higher development efficiency and stronger front‑end capabilities.

Cost

Manpower

Front‑end workload increases; does the team have capacity?

Technical Difficulty

Complex DB, high‑concurrency, offline jobs, or lack of supporting gateway services.

Benefit

Development Efficiency

Reduced integration and testing effort.

Front‑end Capability

Deeper business insight and ownership.

Migration Strategies

Full Migration : rewrite all Java code to equivalent FaaS functions in a dedicated window. High risk, long duration.

Incremental Migration : migrate only when new requirements arrive, gradually converting legacy modules. Lower risk, longer overall timeline.

The team recommends the incremental approach.

Stability Assurance

Key concerns are traffic spikes and fallback mechanisms. Traffic is estimated by average QPS = daily PV / 50,000 and multiplied by a safety factor. Fallback is achieved by caching successful responses in CDN or server cache.

Low‑Code Exploration

The team built the “Zhilang” platform, a visual orchestration tool that generated over 1,000 interfaces for 100+ users. It provides visual composition, full CI/CD pipeline, runtime isolation and an open JSON‑based protocol.

Conclusion

Node‑based FaaS expands front‑end engineers’ capability boundaries, reshapes the production relationship, and creates new value streams. Before starting, evaluate cost/benefit, consider traffic, and plan a gradual migration.