Overview

You can select an appropriate product edition, deployment solution, and deployment mode as needed.

Select an appropriate product edition

OceanBase Database is available in two editions: OceanBase Database Enterprise Edition and OceanBase Database Community Edition.

• OceanBase Database Enterprise Edition: an enterprise-level, native distributed database independently developed by Ant Group. It provides financial-grade high availability on commodity hardware. Its groundbreaking deployment mode of "five IDCs across three regions" sets a new standard for automatic, lossless disaster recovery at the region level. It has also set new records in the TPC-C benchmark test, supporting more than 1,500 nodes in one cluster. It is cloud-native, highly consistent, and highly compatible with Oracle and MySQL.
• OceanBase Database Community Edition: a standalone and distributed integrated database compatible with MySQL, independently developed by Ant Group. It is built on the native distributed architecture and supports enterprise-level features such as financial-grade high availability, transparent horizontal scaling, distributed transactions, multitenancy, and syntax compatibility.

For more information about the differences between the Enterprise Edition and the Community Edition, see Differences between the features of the Enterprise Edition and the Community Edition.

Select an appropriate deployment solution

OceanBase Database supports high availability and disaster recovery at the node, Internet data center (IDC), and region levels. You can deploy OceanBase Database in a single IDC, in two IDCs in the same region, in three IDCs across two regions, or in five IDCs across three regions. You can also deploy the arbitration service to reduce costs.

For more information about each deployment solution, see HA deployment solutions for OceanBase clusters.

Select an appropriate deployment mode

Plan your resources

After you select an appropriate deployment solution, you must plan and prepare the resources required for the deployment. For more information about the configuration requirements for servers, see Prepare servers.

Deploy columnstore replicas

To support TP-enhanced hybrid workloads (near real-time decision analysis scenarios), OceanBase Database provides support for read-only columnstore replicas (Column Store Replica, C replicas). Users can deploy columnstore replicas on independent zones. On a columnstore replica, user tables (including replicated tables but excluding index tables, internal tables, and system tables) are stored in columnar format.

After deploying a columnstore replica (C replica) in the locality of a tenant, a separate set of ODP (ODP V4.3.2+) must be deployed to access the C replica. Configure weak read and columnstore routing on the ODP side so that OLAP requests reach the columnstore replica via methods like weak read. For deployment and configuration steps, see Deploy and use columnstore replicas.

For overall architecture selection, see Typical AP architecture deployment guide.