This topic describes the connection modes and deployment methods for an OBKV-Table cluster.
OBKV connection modes
An OBKV-Table cluster supports two connection modes: direct connection and ODP proxy. The components required for deployment vary with the connection mode.
Direct connection mode
In direct connection mode, the OBKV client directly connects to the OceanBase AI Database cluster. The OBKV client provides routing capabilities, directing data requests to the appropriate OBServer node and returning the execution results to the user.
In direct connection mode, the OceanBase Config Server is required to provide metadata registration, storage, and query services for OceanBase AI Database.
When the RegionServer list of the OBServer cluster changes, the change is pushed to the Config Server. OBKV-Table can then obtain the updated RegionServer addresses from the Config Server in real time. Normally, OBKV-Table can detect changes to the RegionServer list on its own. Access to the Config Server is required only during client initialization or when all RegionServers in the list go offline at the same time.
ODP proxy mode
OceanBase Database Proxy (ODP) acts as a proxy server. User data in OceanBase AI Database is stored as multiple replicas across various nodes. ODP receives RPC requests from the OBKV client, forwards them to the optimal target node, and returns the execution results to the user.
Notice
When using OBKV, the ODP version must be 4.3.1 or later.
Connection mode selection
Direct connection mode has one less hop in the data link than ODP proxy mode, resulting in lower latency. However, it requires exposing the RPC ports of OBServer nodes for client access, which increases port management complexity. In ODP proxy mode, ODP hides the distributed complexity of OBServer nodes and provides connection management, load balancing, and unlimited horizontal scaling. ODP makes it easier to operate and maintain OceanBase AI Database clusters.
Generally, you can choose direct connection mode for private deployments and ODP proxy mode for cloud deployments:
- In public clouds, business clusters and database clusters are network-isolated, so ODP is required to route messages. In private clouds, if you want to decouple your business from the database (for example, to ensure business continuity during database migration), you can also use ODP proxy mode.
- In some private deployment scenarios where the business and database IDCs are network-isolated, consider deploying ODP. By using IP mapping and load balancing components, you can send business requests to ODP, which then forwards them to the database.
OBKV cluster deployment
The components that need to be deployed additionally for an OBKV cluster vary depending on the connection mode:
- For direct connection mode, an OceanBase Config Server must be deployed.
- For ODP proxy mode, ODP must be deployed. Therefore, pay special attention to selecting the corresponding component during deployment.
Select an appropriate deployment solution
Select an appropriate deployment solution as needed.
OceanBase AI Database supports high availability and disaster recovery at the single-machine, IDC (multiple IDCs in the same city; IDC is the general term used in this topic), and city (multiple cities) levels. It supports single-IDC, dual-IDC, two-region-three-IDC, and three-region-five-IDC deployments, and also supports deploying an arbitration service to reduce costs.
Select an appropriate deployment method
Currently, OceanBase Cloud Platform (OCP) is the only supported method for deploying OceanBase AI Database clusters. For specific operations, see Deploy a three-replica OceanBase AI Database cluster by using OCP.
Plan your resources
Before deploying after selecting an appropriate deployment solution, you need to plan and prepare the resources required for the deployment.
For server configuration requirements, see Prepare servers.