Evolution of Xianyu’s Business Architecture: From Trial Phase to Cloud‑Native Integration
Xianyu’s architecture progressed through four stages—trial, growth, platform, and cloud‑native integration—each aligning technical choices with business needs, shifting from rapid hybrid routing to automated services, extensible frameworks, and finally a unified Flutter/Dart stack that cuts development effort, boosts collaboration, and accelerates iteration.
The article presents a case study of Xianyu’s business architecture evolution, showing how the architecture adapts to business growth and supports rapid development.
Business background: Xianyu is a high‑value second‑hand marketplace where trust cost is a key challenge. Market expansion is pursued by lowering newcomer cost and improving matching efficiency.
Architecture evolution is divided into four stages – trial period, growth period, platform period, and cloud‑native integration – each with distinct business problems and architectural focus.
Trial period : Emphasis on speed; quality is traded for response time. A hybrid solution (URL Router, Switch Center, Poplayer) routes requests to H5 when native pages are unavailable, reducing iOS/Android release lag.
Growth period : Focus on efficiency and capability automation. MBaaS provides a SQL‑like data source for the client, while the client side builds a Service Bus and component library to assemble UI from reusable components.
Platform period : Requires extensibility and business isolation. The SWAK framework separates immutable (what to do) from mutable (how/who does it) parts, offering remote extension points for application‑level isolation.
Cloud‑native integration : Unifies the tech stack with Flutter/Dart across client and server. Dart runs on Faas, and the Nexus framework connects UI and logic, achieving an end‑to‑end development model where total effort is less than the sum of separate client and server work (1+1<2). This also reshapes production relationships.
Benefits observed include resource balance (single Flutter codebase replaces iOS and Android), higher collaboration efficiency, closed‑loop business logic, deeper domain focus, and faster iteration, illustrated by the refactoring of an order page.
Conclusion: Architectural evolution is incremental; aligning architecture with current business characteristics is essential for sustainable system efficiency.
Xianyu Technology
Official account of the Xianyu technology team
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.