Overview

You can choose a suitable product edition, deployment scheme, and deployment method as needed.

Choose a suitable product edition

OceanBase Database provides two editions: Enterprise Edition and Community Edition.

• OceanBase Database Enterprise Edition: A fully self-developed enterprise-level native distributed database. It provides financial-grade high availability on general-purpose hardware. It sets a new standard for automatic lossless disaster recovery across five IDCs in three regions. It has set a new world record in the TPC-C benchmark test. It supports more than 1,500 nodes in a single cluster. It is cloud-native, highly consistent, and highly compatible with Oracle and MySQL.
• OceanBase Database Community Edition: A fully self-developed, MySQL-compatible, open-source, integrated database for single-node and distributed deployment. It has a native distributed architecture and supports enterprise-level features such as financial-grade high availability, transparent horizontal scaling, distributed transactions, multi-tenancy, and syntax compatibility.

Choose a suitable deployment scheme

OceanBase Database supports high availability and disaster recovery at the single-node, IDC, and regional levels. You can deploy OceanBase Database clusters in a single IDC, two IDCs, three IDCs in two regions, or five IDCs in three regions. You can also deploy an arbitration service to reduce costs.

For more information about each deployment scheme, see Overview of OceanBase cluster high availability deployment schemes.

Choose a suitable deployment method

Plan your resources

Before you deploy OceanBase Database, you need to plan and prepare the resources required for the deployment.

• For more information about the server configuration requirements, see Prepare servers.

Deploy columnstore replicas

To support hybrid workloads such as TP and AP, OceanBase supports deploying read-only columnstore replicas (C replicas) on independent zones.

Columnstore replicas can be deployed in two ways:

• Before V4.6.0, weak-consistency columnstore replicas require an independent ODP for configuration and request routing settings.

• From V4.6.0 onwards, strong-read columnstore replicas do not require an independent ODP. They can share the same ODP with rowstore replicas, with routing strategies automatically selected by the database.

For detailed steps, see Deploy and use columnstore replicas. For architecture selection, refer to Typical AP architecture deployment guide.