OceanBase Database is available in two editions: OceanBase Database Enterprise Edition and OceanBase Database Community Edition.
OceanBase Database Enterprise Edition is an enterprise-level, native distributed database independently developed by the OceanBase team. 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. OceanBase Database 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 is a standalone distributed and integrated database compatible with MySQL. 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. OceanBase Database Community Edition has an open-source kernel and provides open APIs and various eco-capabilities to meet the business requirements of enterprises or individuals.
For more information about the differences between the Enterprise Edition and the Community Edition, see Differences between the Enterprise Edition and the Community Edition.
This topic describes the deployment methods and scenarios of the two editions of OceanBase Database.
Deployment methods
OceanBase Database Enterprise Edition
- Use OceanBase Cloud Platform (OCP) to deploy an OceanBase cluster
- Use OceanBase Deployer (obd) to deploy an OceanBase cluster
- Use the CLI to deploy an OceanBase cluster
OceanBase Database Community Edition
- Use obd to deploy an OceanBase cluster
- Use OCP to deploy an OceanBase cluster
- Use the Docker image to deploy an OceanBase cluster
- Use ob-operator to deploy an OceanBase cluster in a Kubernetes environment
Deployment scenarios
OceanBase Database Enterprise Edition
In a production environment, we recommend that you use OCP to deploy an OceanBase cluster. For more information, see Deploy a three-replica OceanBase cluster by using OCP.
In a non-production environment, you can use the CLI to deploy an OceanBase cluster. For more information, see Deploy a three-replica OceanBase cluster by using the CLI.
For experience purposes in a non-production environment, you can use obd to deploy an OceanBase cluster. For more information, see the Solution 1: Deploy OceanBase Database in a demo environment or Solution 2: Deploy an OceanBase cluster section in Quick start with OceanBase Database Community Edition.
OceanBase Database Community Edition
If you want to have a quick experience with OceanBase Database in a non-natively supported operating system such as macOS and Windows, we recommend that you use the Docker image for deployment. For more information, see the Solution 3: Deploy OceanBase Database in a container section in Quick start with OceanBase Database Community Edition.
If you want to have a quick experience with OceanBase Database in a natively supported operating system such as Linux, we recommend that you use obd for deployment. For more information, see the Solution 1: Deploy OceanBase Database in a demo environment or Solution 2: Deploy an OceanBase cluster section in Quick start with OceanBase Database Community Edition.
In an online environment, we recommend that you use obd for standard deployment. For more information, see Deploy an OceanBase cluster through the GUI of obd.
In a Kubernetes environment, we recommend that you use ob-operator for deployment. For more information, see Deploy OceanBase Database in a Kubernetes cluster.
References
- For more information about the deployment process of OceanBase Database Enterprise Edition, see Deployment process.
- For more information about the deployment process of OceanBase Database Community Edition, see Overview.
- For more information about obd, see What is obd.