Evolution of Xianyu Transaction Link Architecture: From Frontend Decoupling to Cloud‑Native Integration

Following the Double‑Eleven sales peak, Xianyu needed to ensure a stable and high‑performance transaction chain for billions of orders. This article presents a technical case study of the Xianyu transaction link architecture evolution from a client‑development viewpoint.

The link supports multiple business types (C2C, guarantee, virtual‑currency, etc.) and numerous states, requiring both stability and limited dynamic capabilities. Initial efforts focused on decoupling business logic and introducing page block‑level modularization.

Three stages are described:

Stage 1 – Business Decoupling: Backend split into data model, C2X domain, and solution layer; frontend parses data into ViewModel and renders block components.

Stage 2 – Dual‑End Integration & Cloud Migration: Adopted Flutter + FishRedux for cross‑platform UI, introduced a common action center, and began moving business logic to the cloud.

Stage 3 – Cloud‑Native One‑Stop Development: Unified stack using Dart, FaaS (Dart Runtime), and Flutter, allowing frontend engineers to write server‑side glue code, reducing team size and improving efficiency.

The cloud‑native approach separates rendering interfaces from interaction interfaces, enabling dynamic operation configuration and seamless action routing via the Nexus framework. The result is a streamlined development process—e.g., the order page now requires a single developer instead of three—demonstrating significant gains in productivity and scalability.