Deployment

The deployment of OBKV-HBase comprises two parts:

• Deploy an OBKV cluster: An OBKV cluster is actually an OceanBase cluster for a MySQL tenant. For more information about how to deploy an OceanBase cluster, see Deployment overview.

• Configure the OBKV client: The configuration of the OBKV client can slightly differ depending on whether you deploy your cluster in a public cloud or a private environment.

Deploy an OBKV cluster

You can select an appropriate product form, deployment solution, and deployment method as needed.

Select an appropriate product form

OceanBase Database is available in two forms: OceanBase Database Enterprise Edition and OceanBase Database Community Edition. At present, OceanBase Database Community Edition supports only the direct connection mode and OceanBase Database Enterprise Edition supports both direct connection and connection through OceanBase Database Proxy (ODP). You can select a product form as needed.

Select an appropriate deployment solution

OceanBase Database uses a shared-nothing architecture with multiple replicas to ensure zero single point of failure (SPOF) and system continuity. You can deploy an OceanBase cluster in a single IDC, dual IDCs, three IDCs across two regions, and five IDCs across three regions. OceanBase Database supports high availability and disaster recovery at the single-IDC, multi-IDC (in the same region), and region level. 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 method

Plan resources

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

• For server configuration requirements, see Prepare servers.

Configure the OBKV client

The following figure shows the differences when OBKV-HBase is deployed in a public cloud and in a private environment.

Direct connection mode

When you deploy OBKV-HBase in a private environment, you can choose the direct connection mode.

• The Config Server of OceanBase Database provides metadata registration, storage, and query services.
• The client of OBKV-HBase comes with the data routing feature. In direct connection mode, data is directly delivered to the destination data node.
• When the RegionServer list of an OceanBase cluster changes, the changes will be pushed to the Config Server. OBKV-HBase can obtain the RegionServer list from the Config Server in real time. Generally, OBKV-HBase can detect the changes in the RegionServer list by itself. If the client is initialized and the RegionServer list is offline, OBKV-HBase needs to access the Config Server.

Public cloud mode

When OBKV-HBase is deployed in a public cloud, network isolation exists between the business and database clusters. In this case, ODP is required to route messages.