This topic describes how to deploy OceanBase Database Proxy (ODP).
The deployment mode varies based on the actual physical environment and business requirements. When you deploy ODP in a production environment, take the following factors into consideration:
Delivery mode
ODP is delivered as an RPM package and can be deployed by using OceanBase Deployer (obd), OceanBase Cloud Platform (OCP), or the CLI.
Quantity
The number of ODPs that can be deployed is relevant with the number of applications or OBServer nodes, depending on the specific deployment mode.
Deployment mode
The deployment modes supported for ODP differ in the response time and resource contention. The performance varies significantly based on the deployment mode. ODP can be deployed independently or together with OceanBase Database.
Deploy ODP together with OceanBase Database
When you deploy OceanBase Database, you can deploy an ODP process on the server where OceanBase Database resides, forming a 1:1 correspondence between the OBServer node and the ODP. In this deployment mode, the number of ODPs is irrelevant with the number of applications. You can also deploy one ODP in each zone.
The following figure shows a common ODP deployment mode in a private cloud. You must deploy and configure the load balancer.
Deploy ODP independently
You can deploy ODP on an independent server. The number of ODPs is irrelevant with the number of applications or OBServer nodes, and is determined based on actual business requirements.
We recommend that you use a midrange computer, for example, an Elastic Compute Service (ECS) instance with 16 CPU cores and 16 GB of memory. If ODP is deployed independently, it does not contend for resources with OceanBase Database. You can better manage ODP and use ODP as a resource pool to provide external services. This deployment mode has been applied in the public cloud.
Note
You must deploy and configure the load balancer.