Evolution of Xianyu Transaction Chain Architecture: From Decoupled Frontend to Cloud‑Native One‑Stop Development

After the Double‑Eleven shopping festival generated a staggering 268.4 billion CNY in sales, Xianyu needed to ensure the stability and speed of its transaction chain. This article examines the architecture evolution of Xianyu’s transaction flow from a client‑centric perspective, focusing on performance, development efficiency, and scalability.

The transaction chain supports multiple business types (ordinary C2C, meet‑up, escrow, virtual currency, player‑to‑player, recycling, consignment, etc.) and various states, requiring a flexible yet performant solution.

**Stage 1 – Business Decoupling** (2017‑2018) introduced page block‑level modularization. The backend was split into three layers: data model, Xianyu C2X transaction domain, and business solutions. The client parsed backend data into a ViewModel and rendered page blocks dynamically.

Key techniques: page blockization and action‑based operations.

**Stage 2 – Dual‑End Integration & Gradual Cloud Migration** (2019) solved client‑server logic inconsistency by adopting Flutter for cross‑platform development and FishRedux for page modularization. A common action center unified transaction operations, and business logic began moving to the cloud while the client retained only the rendering layer.

Key components: Flutter + FishRedux, transaction operation center, partial business cloud migration.

**Stage 3 – Cloud‑Native One‑Stop Development** unified the technology stack with Dart, leveraging FaaS (serverless) and a Flutter + Dart Runtime backend. Frontend developers now write server‑side glue code, eliminating traditional operations and enabling end‑to‑end development loops.

In this model, the server focuses on domain construction, while the client aggregates domain data, generates rendering protocols, and directly renders UI. The rendering interface supplies page data, and actions are dynamically configurable based on order state and business type.

**Results**: The cloud‑native version of the order page reduced the development team from three to one, significantly cutting coordination overhead and boosting productivity. The new architecture is being rolled out to other transaction scenarios.

**Future Plans**: Continue applying the cloud‑native approach to additional transaction flows, using the Xianyu transaction chain as a template for broader architectural evolution.