Xianyu's Cloud-Native Serverless Architecture Journey

01 Why Serverless?

Xianyu, Alibaba’s C2C marketplace, grew from a small internal project to a platform with GMV of 2000 billion RMB and over 30 million daily active sellers. Rapid growth required a more flexible and efficient development model.

Traditional monolithic architecture caused unclear boundaries, high coordination cost, long development cycles, and heavy operational overhead.

Unclear separation between client, glue layer, and domain leads to high collaboration cost.

Monolithic services create coupling in development, release, and operations, threatening stability.

Operations cost is high; even small internal apps must follow strict release procedures.

Serverless offers cloud‑native, integrated development, reducing coordination cost and providing a finer‑grained way to split glue‑layer services compared to micro‑services.

02 Exploration and Practice

Since 2018 Xianyu explored Serverless in four stages: self‑built Dart server, FaaS platform, cloud‑native integration, and Serverless transformation of legacy monoliths.

Key milestones include a 2‑second cold‑start Dart server, collaboration with the Gaia FaaS platform, creation of the Nexus API framework to unify Flutter UI and FaaS logic, and the development of GCLI to standardize the development lifecycle.

Four major achievements:

Unified programming model (Nexus API) bridging Flutter and FaaS.

Standardized CLI tooling (GCLI) for consistent local development.

Backend‑as‑a‑Service (BaaS) simplification of storage, messaging, and search.

Cloud‑native engineering integration across multiple services.

These efforts reduced development man‑days by ~30 % and bug density by ~20 % for medium‑large features.

03 Challenges and Solutions

Key technical challenges include heterogeneous Java clients, unified development environments, and domain‑interface familiarity.

Solutions: side‑car proxies for Java, Docker‑based GCLI for environment consistency, and a metadata center for domain services.

Remaining open questions involve Service‑vs‑Serverless selection, function reuse, and unified dependency upgrades.

04 Lessons and Reflections

Serverless is suitable for scenarios demanding rapid iteration, cost efficiency, and flexible scaling, but requires mature ecosystems and careful security considerations.

Organizationally, Serverless reshapes communication structures, encouraging cross‑functional teams and broader domain knowledge among front‑end engineers.

05 Outlook

Xianyu continues to migrate its giant monolith to Serverless, aiming to complete the transformation within 3‑6 months.

Industry surveys show strong interest in Serverless across software, finance, and startup sectors, while security and vendor lock‑in remain concerns.