This topic describes the specifications and billing rules of the database proxy service.
Background information
To provide a better resource allocation and cost structure for the database proxy service, and to offer a more flexible and reliable deployment architecture to meet the needs of different customers, the product team plans to make important adjustments to the billing mode and deployment options of Exclusive tier of the database proxy service.
The updates to the database proxy service will be implemented gradually through different channels. The current versions are as follows:
Instances from the AWS channel support the new configuration method and the latest billing method, including the free quota for Shared tier and the billing rules for Exclusive tier.
Instances from the Alibaba Cloud channel will continue to use the original configuration method and billing rules.
Billing for database proxy instances from the AWS channel
Tiers
The database proxy service offers Shared and Exclusive tiers.
Shared tier
Computing resources are shared with other customers. OceanBase Cloud allocates the corresponding database proxy specifications based on the number of CPU cores in the cluster. This tier is suitable for scenarios with relatively stable and average traffic. OceanBase Cloud provides the database proxy service with Shared tier for free.
The maximum free quota for Shared tier is calculated as follows: the total number of CPU cores for all proxy clusters in an OceanBase cluster is 1/4 of the total number of CPU cores in the OceanBase cluster. For example, if an OceanBase cluster is deployed in a dual-IDC deployment with 16 CPU cores, the maximum free quota for Shared tier is 16 * 2 / 4 = 8 CPU cores. You can create one proxy cluster with 4 CPU cores or two proxy clusters with 2 CPU cores each. The minimum specification for a single proxy node is 0.25 CPU cores.
Exclusive tier
Exclusive tier provides exclusive CPU resources, ensuring more stable and reliable performance. Compared to Shared tier, Exclusive tier supports larger specifications. You can flexibly adjust the database proxy resource specifications as needed, making them suitable for high-concurrency and high-traffic scenarios.
Billing for Exclusive tier
Note
The prices listed below are for reference only. The actual prices may vary depending on the region and time. Please refer to the prices displayed on the order page for the most accurate information.
The billing rule for Exclusive tier is: Total cost = (Cost per CPU core per hour) × (Number of CPU cores per node) × (Number of nodes) × (Duration)
| Region | Unit | USD/CPU/hour |
|---|---|---|
| All regions (excluding São Paulo) | 1 vCPU (1 core, 2 GiB) | 0.120 USD |
| São Paulo | 1 vCPU (1 core, 2 GiB) | 0.155 USD |
Example:
Consider an instance in the AWS channel in São Paulo, deployed in a dual-IDC deployment (1-1). The database proxy is configured with Exclusive tier, deployed in a dual-IDC primary-standby deployment. Each proxy node has a specification of 1 core and 2 GiB of memory. The actual usage duration is 24 hours.
Total cost of the database proxy: 0.155 USD/hour/core × 1 core × 2 nodes × 24 hours = 7.44 USD
Billing for database proxy instances from the Alibaba Cloud channel
Tiers
The database proxy service offers Shared and Exclusive tiers.
Shared tier
Shared tier share computing resources with other customers. OceanBase Cloud allocates the corresponding database proxy specifications based on the number of CPU cores in the cluster. This specification is suitable for scenarios with relatively stable and average traffic. OceanBase Cloud provides the database proxy service with Shared tier for free.
The maximum specification for the database proxy is 1/4 of the total number of CPU cores in the database cluster multiplied by the number of full-featured replicas.
Exclusive tier
Exclusive tier provides exclusive CPU resources, ensuring more stable and reliable performance. Compared to Shared tier, Exclusive tier supports larger configurations. You can flexibly adjust the database proxy resource specifications as needed, making them suitable for high-concurrency and high-traffic scenarios.
Billing for Exclusive tier
The billing rule is: Total cost = (Cost per CPU core per hour) × (Number of CPU cores per zone) × (Number of zones) × (Duration). The number of zones is 2 for a dual-IDC deployment and 3 for a triple-IDC deployment. Adding read-only replicas does not increase the number of zones for the database proxy.
Note
Maximum number of connections: By default, each database proxy endpoint supports up to 5,000 connections. After you create a database instance and one tenant, OceanBase Cloud automatically creates one primary endpoint, which supports up to 5,000 connections by default. If you need to support more connections, please contact technical support.
| Cloud vendor | Region | Unit | USD/CPU/hour |
|---|---|---|---|
| Alibaba Cloud | Hong Kong (China) | 1 vCPU (1 core, 2 GiB) | 0.14 |
| Alibaba Cloud | Singapore (Singapore) | 1 vCPU (1 core, 2 GiB) | 0.14 |
| Alibaba Cloud | Jakarta (Indonesia) | 1 vCPU (1 core, 2 GiB) | 0.14 |
| Alibaba Cloud | Frankfurt (Germany) | 1 vCPU (1 core, 2 GiB) | 0.14 |
Example:
Consider a database instance in Singapore, deployed in a dual-IDC deployment (2F1A). The database proxy is configured with Exclusive tier, with a specification of 8 cores and 16 GiB of memory per zone. The actual usage duration is 24 hours. Total cost of the database proxy: 0.14 USD/hour/core × 8 cores × 2 zones × 24 hours = 53.76 USD