How Alibaba’s “Wǔcǎi Shí” Project Reinvented Backend Architecture with Shared Services

1. Solving Business Scalability

The Wǔcǎi Shí project did not evolve from the Taobao or Tmall architecture; it underwent a thorough reconstruction, representing a new era of distributed technology.

Before integration, the architecture resembled that of non‑Internet software vendors: a commercial database, minicomputers, high‑end storage, and an end‑to‑end monolithic system.

Each business module was an independent system sharing data only via the database, without a common service layer. This design allowed small teams to develop quickly, with simple operations and high stability.

As business complexity grew, several challenges emerged:

Low development efficiency and limited reusability of business modules.

Weak system scalability due to database connection limits and server capacity.

Technical upgrades constrained by the need to modify multiple systems for a single change.

To address the business scalability issue, a shared‑service layer was established, extracting common business elements into reusable services. For example, member services, product services, transaction services, marketing services, inventory, logistics, etc., were abstracted so any system could obtain the needed data via a unified API.

Horizontal services such as Mobile Taobao, security, and merchant services rely heavily on this shared layer, achieving consistent data and unified interfaces.

2. Solving Technical Scalability

Technical scalability required middleware to handle distributed concerns. Alibaba built the HSF framework to provide service discovery, routing, and same‑rack preference mechanisms.

Database sharding and partitioning were encapsulated in the TDDL framework, while asynchronous transaction handling and eventual consistency were achieved with a publish‑subscribe system called Notify.

These three components—HSF, TDDL, and Notify—effectively resolved the technical challenges introduced by a distributed architecture, keeping the system as simple to develop as a single‑machine application.

When compute capacity is insufficient, scaling is achieved simply by adding more servers; the shared‑service layer and middleware isolate frequent business changes and technical evolution within appropriate system boundaries.

Conclusion

By extracting a shared‑service layer, Alibaba dramatically reduced the cost of trial‑and‑error, enabling rapid emergence of new business markets and accelerating e‑commerce growth. Introducing distributed middleware solved technical scalability, allowing the system to expand simply by adding servers while keeping developers insulated from the complexities of distribution.

The architectural principles and middleware technologies pioneered in the Wǔcǎi Shí project have been widely adopted across Alibaba’s subsequent business and technical evolution and have influenced many other internet companies.