Ant Financial’s Cloud‑Native Hybrid Architecture for Financial Services

Ant Financial has reshaped payments over the past fifteen years, serving more than 1.2 billion users, and at the 2019 Hangzhou Cloud Conference it shared its technical evolution and future fintech innovations.

Entering the cloud‑native era, the financial industry must adopt cloud‑native practices; Ant Financial has applied hybrid‑cloud solutions for the past two years, addressing openness, internetization, and strict regulatory compliance, concluding that a hybrid‑cloud strategy best fits financial institutions.

Ant’s high‑availability design uses a three‑city five‑center active‑active architecture, delivering city‑level disaster recovery, low‑cost transactions, unlimited scalability, and metrics such as RPO = 0 and PTO < 30 seconds.

To build a financial‑grade online transaction system, Ant leverages SOFAStack and OceanBase, which provide high availability (99.99 %+), strong consistency, horizontal scalability across applications and databases, and high performance through read‑write separation and in‑memory optimizations.

Financial‑grade security is addressed in three cloud‑native layers: network security (policy‑driven traffic control, encryption, traffic analysis), infrastructure security (secure containers, isolated kernels, sandboxes), and business security (SOFAEnclave confidential computing, memory‑safe Enclave LibOS Occlum).

The transition from unitization to an elastic architecture involves routing user requests at the network edge based on sharding, deploying a Kubernetes cluster per unit, and using a federated API server with ETCD metadata; ETCD’s limitations are overcome by moving its KV store to OceanBase, achieving multi‑city consistency.

Heterogeneous customer infrastructures and legacy systems are handled with a dual‑mode PaaS that supports both traditional VM‑style deployments and container‑based workloads, using extensions like CAFEDeployment to enable graceful gray‑release, rollback, and large‑scale cluster operations.

Dual‑mode micro‑services are realized through a Mesh architecture that works with sidecars in Kubernetes and agents for legacy environments, integrating control‑plane services with existing registration mechanisms to ensure global service visibility and routing.

Serverless adoption is illustrated by optimizing Java startup times: Ant uses JVM SVM static compilation to reduce Java service cold‑start from ~60 seconds to ~4 seconds, encapsulated in the SOFA Serverless Container and SOFA Function, enabling rapid scaling and isolation.

In summary, achieving a financial‑grade hybrid cloud requires an evolvable, iterative approach across PaaS, micro‑services, and serverless layers, providing dual‑mode capabilities that bridge legacy systems with modern cloud‑native practices.