Evolution of Alipay’s Technical Architecture for Double 11 (2009‑2023): From SOFA to OceanBase and Cloud‑Native

Alipay’s Double 11 experience began in 2009 when the first large‑scale promotion forced the team to build a SOA‑based accounting system and adopt the self‑developed SOFA middleware, replacing the earlier WebX framework.

From 2010 to 2013 the platform tackled rapid traffic growth by vertically splitting databases, introducing horizontal scaling, and deploying the two‑phase‑commit XTS transaction middleware (now open‑sourced as Seata). During this period OceanBase was initiated, and a custom load‑balancer (Spanner) was launched to handle peak loads.

Between 2014 and 2018 Alipay pursued the “去IOE” (remove Oracle) strategy, scaling OceanBase to handle up to 100 % of transaction and payment traffic, achieving top TPC‑C benchmark results. The era also saw the introduction of full‑link stress testing, elastic LDC architectures, hybrid online/offline deployments, intelligent customer service, AI‑driven risk control, and the first use of blockchain and biometric payments in Double 11.

Since 2019 Alipay has embraced cloud‑native principles, deploying the SOFAMesh‑based Service Mesh at massive scale, launching a financial‑grade cloud‑native platform, and building an open computing architecture that unifies batch, streaming, graph, and machine‑learning workloads. OceanBase 2.2 now supports both MySQL and Oracle protocols, processing 61 million transactions per second during Double 11.

The article concludes that continuous technical innovation—spanning distributed databases, big‑data processing, cloud‑native infrastructure, and security—has turned Double 11 from a sales event into a catalyst for Alipay’s broader fintech evolution.