Database proxy billing

This topic describes the specifications and billing rules of the database proxy service.

Background information

To optimize the resource configuration and cost structure of the OB Cloud database proxy (ODP) service and provide more flexible and reliable deployment architectures for different business scenarios, the product team plans to make significant adjustments to the billing mode and deployment options for Exclusive tier 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, Fusion, and Exclusive tiers.

• Shared tier

  Computing resources are shared with other customers. OceanBase Cloud allocates database proxy specifications based on the number of CPU cores in the cluster. Shared tier is suitable for workloads with relatively stable and evenly distributed 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-zone 16 vCPUs (1-1) configuration, the maximum free quota for Shared tier is 16 vCPUs × 2/4 = 8 vCPUs. You can create one dual-node proxy cluster with 4 vCPUs per node, two dual-node proxy clusters with 2 vCPUs per node, or another equivalent combination. The minimum specification of a single proxy node is 0.25 vCPU.

• Fusion tier

  Only some cloud vendors offer Fusion tier. A Fusion proxy cluster shares computing resources with your OceanBase cluster and is not included in the calculation of the free quota.

  For example, if an OceanBase cluster is deployed in a dual-zone 16 vCPUs (1-1) configuration, the maximum total quota for Shared tier under this OceanBase cluster is 16 vCPUs × 2/4 = 8 vCPUs. Users can create one 4 vCPUs dual-zone deployment proxy cluster, or two 2 vCPUs dual-zone deployment proxy clusters and so on so forth. The cumulative number of nodes * the specification per node of all proxy clusters must not exceed the total quota.

  If you already have three 2 vCPUs dual-zone deployment Shared proxy clusters and one 6 vCPUs Fusion proxy cluster, then you have exceeded the quota by a total of 2 vCPUs × 2 × 3 - 8 = 4 vCPUs (Fusion clusters are not counted towards the existing Shared clusters). In the future, you need to release the Shared clusters exceeding 4 vCPUs before you can continue creating Shared proxy clusters. Before that, you cannot create a Shared cluster or increase the specification of a Shared cluster in a configuration change.

• Exclusive tier Dedicated specifications use exclusive physical CPU resources to provide more stable and reliable performance. Compared with Shared tier, Exclusive tier supports larger configurations and allow you to flexibly adjust database proxy resources based on your business requirements. They are suitable for high-concurrency and high-traffic workloads.

Billing for Exclusive tier

• Billing rule Total cost for database proxy = Price per vCPU‑hour × Number of vCPU per node × Number of nodes × Duration.

• Pricing

  Note

  • The price per vCPU‑hour in the following table are reference prices for a single CPU core, namely 1 core and 2 GiB memory, in a single availability zone in the specified region of the corresponding cloud provider.
  • The prices in the following table are for reference only. Actual prices may vary by region, time, and other factors. The prices displayed on the actual order page shall prevail.

  Cloud vendor	Region	Resource billing unit	Price per vCPU‑hour (USD)
  AWS	Regions except São Paulo	1 vCPU (1 vCPU, 2 GiB memory)	0.120
  AWS	São Paulo	1 vCPU (1 vCPU, 2 GiB memory)	0.1550

• Billing example Assume that an AWS instance in São Paulo uses a database 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: USD 0.155 vCPU‑hour × 1 vCPU × 2 nodes × 24 hours = USD 7.44.

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

• Billing rule

  Note

  Maximum number of connections: By default, each database proxy address supports up to 5,000 connections. After you create a database instance and a tenant, a primary address is automatically created. By default, this address supports up to 5,000 connections. To increase this limit, contact technical support.

  Total cost for database proxy = Cost per CPU core per hour × Number of CPU cores per zone × Number of zone × 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.

• Price table

• Billing example

  Assume that a database instance in Frankfurt uses 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: USD 0.14 vCPU‑hour × 8 vCPU × 2 zones × 24 hours = USD 53.76.