With the advancements of digital transformation, industrial data is experiencing an exponential increase in volume and access concurrency. Enterprises from industries such as finance, insurance, and communications expect more powerful disaster recovery capabilities to protect their core businesses against IDC-level or city-wide failures. They need solutions to achieve high availability and disaster recovery of services at the server, IDC, and city levels and quickly complete a failover in the event of a disaster to minimize the blast radius of failures without data loss. The solutions must also support the management and operation of various application systems, including core business systems. Through years of real-world experience in supporting the core systems of Alipay and MYbank, OceanBase has developed a database architecture that features active geo-redundancy with five IDCs deployed across three regions. The architecture provides benchmark cases demonstrating the industry-leading capabilities of OceanBase Database in supporting core systems that have extremely high data consistency and availability requirements.
OceanBase Database implements geo-disaster recovery based on the multi-replica and multi-region architecture and the highly efficient Paxos consensus protocol. In this architecture, OceanBase clusters can be deployed in five IDCs across three regions, with data replicas stored in local and remote IDCs. Based on this architecture, OceanBase Database supports the Logical Data Center (LDC) deployment mode. In addition, applications are transformed into microservices based on middleware, such as the Scalable Open Financial Architecture (SOFA) platform from Ant Group. Therefore, the blast radius of a failed business LDC can be reduced to 1%, and services can be automatically restored within 1 minute in the event of a city-wide fault, with zero data loss. With the new arbitration service which provides voting capabilities for Paxos with low resource requirements, OceanBase Database V4.x supports IDC-level disaster recovery in the architecture of three IDCs across two regions and greatly reduces the overall cost of resources (such as cross-city network bandwidth and hardware) of the third IDC. When any IDC fails, the database response time remains unchanged, meeting the needs of enterprises.