How Alipay’s Tech Team Turned ‘Impossible’ Double‑11 Peaks into Seamless Transactions

From 2009 to 2019: The Evolution of Alipay’s Double‑11 Engine

In 2009, Alipay engineers faced a sudden surge of transactions during the first “Double‑11” promotion, manually expanding capacity and racing against a looming outage.

Each year the target grew—what seemed impossible became reality—driving a culture of relentless scaling and “Chinese speed.”

Early Challenges and Manual Scaling

Engineers like Chen Liang monitored transaction volume in real time, adding servers as the traffic approached limits. When the accounting database ran out of capacity, they cut non‑essential services to keep payments alive.

Architectural Revolution

By 2012 the team introduced a unit‑based architecture, and in 2013 began the LDC project to redesign the system, aiming for a peak of 20,000 transactions per second.

Oracle’s connection limits and power constraints forced a shift to a self‑developed distributed database, OceanBase.

OceanBase Takes the Stage

After rigorous testing, OceanBase handled the 10% traffic slice that Oracle could not, proving its reliability and later becoming the core transaction database for all of Ant Financial.

Its performance improvements—from 10 ms to sub‑1 ms response times—enabled the system to support billions of daily transactions.

Full‑Link Stress Testing

From 2014 onward, the team built a comprehensive stress‑testing platform, turning “impossible” goals into measurable metrics and catching hidden bugs before they could affect users.

Cloud‑Native and Future Vision

Since 2019, Alipay has migrated to cloud‑native infrastructure, allowing dynamic scaling, resource sharing, and automated fault handling, aiming for a future where the system runs itself.

Through eleven years of “miracle engineering,” Alipay turned a modest promotion into a global e‑commerce powerhouse.