This topic describes the pricing and billing details for OceanBase Cloud Binlog service.
Overview
The Binlog service of OceanBase Cloud is a service that collects the commit logs (Clogs) of OceanBase Database and converts them into MySQL Binlog. It is mainly used for scenarios such as real-time data subscription. The Binlog service currently supports the pay-as-you-go billing method where users pay based on generated billing orders. The price is determined based on the final configuration of the Binlog instance, including the cloud vendor, region, compute unit, and storage space.
Billing descriptions
Billing method
At present, Binlog service supports pay-as-you-go billing.
Billing items
The billing items for Binlog service on OceanBase Cloud include compute units and storage space. The Binlog service in the Running state allows you to change its configuration. For more information, see Change configuration.
Compute units
A compute unit refers to the capabilities of the Binlog service to collect and convert Clogs and provide subscription services. Each compute unit provides the following capabilities.
Binlog conversion capability: Converts Clogs collected from OceanBase databases into MySQL Binlog. The actual conversion capability is determined by the limit of Rows Per Second (RPS) or Bytes Per Second (BPS), whichever is reached first.
One compute unit provides a maximum of 200 RPS, which means it can convert up to 200 rows per second.
One compute unit provides a maximum of 0.2 MiB BPS, which means it can convert up to 0.2 MiB of Clogs per second.
Binlog subscription capability: Provides converted MySQL Binlog for subscriptions. The actual subscription capability is determined by the limit of Rows Per Second (RPS) or Bytes Per Second (BPS), whichever is reached first.
Each subscription connection under one compute unit provides a maximum of 200 RPS, which means it can subscribe to up to 200 rows per second.
Each subscription connection under one compute unit provides a maximum of 0.2 MiB BPS, which means it can subscribe to up to 0.2 MiB of Binlog per second.
Binlog subscription connections: Each compute unit provides one subscription connection. However, the maximum number of subscription connections can be up to 20. After reaching the maximum number, the number of subscription connections does not increase with the addition of more compute units.
Storage space
Storage space refers to the space used by the Binlog service to store converted Binlog files. You are charged based on the size of the storage space. Binlog storage space can be configured in the following two ways:
Specify storage space: Purchase a fixed storage space. The Binlog service charges you based on the storage space you purchase.
Auto-scale storage space: Configure an auto-scaling strategy. The Binlog service charges you based on the current storage space.
Notice
The actual storage occupied by Binlog files is also affected by the retention duration of the files.
Specifications of billing items
Note
The following specifications are for reference only. In actual scenarios, the specifications may be affected by factors such as hot table updates and large-scale data imports. Please configure the specifications based as needed.
Compute units
Binlog conversion capability: You can calculate the needed Binlog conversion capability based on the transaction log rate of the OceanBase Database tenant. To evaluate the transaction log rate, perform the following steps:
Obtain the transaction log volume for more than a week to determine the reasonable rate of transaction logs (typically recommended for smooth runtime data). For example, if the rate is 10 MiB/s, multiply it by the Binlog expansion coefficient of 1.2 to get the Binlog conversion rate of 12 MiB/s. Each compute unit provides 0.2 MiB/s conversion capability, so you need 12/0.2 = 60 compute units.
For details about how to obtain the transaction log volume of a transactional instance, see Monitor transactions. For details about how to obtain the transaction log volume of an analytical instance, see Monitor database performance.
Also, the Binlog conversion is limited by the rows per second (RPS) capability of compute units with an assumed size of each row of 1 KiB. You need to evaluate the size of the changed data rows. If the data rows are larger than 1 KiB, use the number of compute units obtained in the previous step. If the data rows are smaller than 1 KiB (for example, 0.5 KiB), you need more compute units to process more rows (1 KiB/0.5 KiB * 60 = 120 compute units).
Note
You can obtain the storage size and number of rows of a database table to evaluate the size of each data row.
Binlog subscription capability: If you do not have significant latencies in downstream consumption and need to increase the subscription consumption rate, you can directly use the Binlog conversion capability to calculate the number of compute units. Otherwise, please expand the number of compute units based on your actual needs.
Binlog subscription connections: You can reasonably evaluate the required number of subscription connections based on the downstream business needs. If the number of subscription connections provided by the current compute units cannot meet the business needs, please expand the number of compute units based on your actual needs.
Note
The Binlog service provides a maximum of 20 subscription connections. If you have special requirements, please contact technical support.
Storage space
The retention duration of Binlog files is also limited by the storage space and the log retention duration (default value: 18 hours). When either the retention duration or the storage space reaches its upper limit, Binlog log files will be recycled. Please configure the storage space based on the actual needs of the downstream business. We recommend that you always select the automatic scaling strategy for storage space.
Prices
Compute units
Cloud vendor Region Price per compute unit (CU) All All 0.0200 USD/hour -
Storage space
Cloud vendor Region code Region name Price per storage space (GiB) Huawei Cloud ap-southeast-1 Hong Kong 0.000411 USD/hour GCP asia-southeast2 Jakarta 0.000303 USD/hour asia-southeast1 Singapore 0.000256 USD/hour asia-east2 Hong Kong 0.000256 USD/hour us-west1 Oregon 0.000233 USD/hour asia-northeast1 Tokyo 0.000303 USD/hour us-east4 Northern Virginia 0.000256 USD/hour Azure malaysiawest Malaysia West 0.000119 USD/hour eastus2 East US 2 0.00011 USD/hour southeastasia Southeast Asia 0.000132 USD/hour northeurope North Europe 0.00011 USD/hour AWS eu-central-1 Frankfurt 0.000156 USD/hour ap-south-1 Mumbai 0.00015 USD/hour ap-east-1 Hong Kong 0.000145 USD/hour ap-southeast-1 Singapore 0.00015 USD/hour us-west-1 Northern California 0.00015 USD/hour us-east-1 Virginia 0.00011 USD/hour us-west-2 Oregon 0.00011 USD/hour ap-southeast-5 Malaysia 0.000123 USD/hour ap-northeast-1 Tokyo 0.000163 USD/hour sa-east-1 Sao Paulo 0.000208 USD/hour us-east-2 Ohio 0.00011 USD/hour eu-west-3 Paris 0.000127 USD/hour ap-southeast-3 Jakarta 0.000137 USD/hour Alibaba Cloud ap-southeast-1 Singapore 0.00027 USD/hour eu-central-1 Frankfurt 0.00027 USD/hour ap-northeast-2 Korea 0.00048 USD/hour ap-southeast-5 Jakarta 0.00027 USD/hour cn-hongkong Hong Kong 0.00027 USD/hour ap-southeast-3 Kuala Lumpur 0.00027 USD/hour
Free quota
To facilitate your use of the Binlog service on OceanBase Cloud, each Binlog service instance is granted a certain amount of free quota.
Compute units: The free quota is allocated based on the tenant specification. Specifically, the number of compute units is equivalent to the total number of CPU cores across all units multiplied by the CPU specification per unit (Unit count × Unit CPU specification).
Storage space: 10 GiB of storage space is provided as the free quota.
When the Binlog service pushes the billing data, it calculates the actual resources that need to be charged in real-time. The actual resources that need to be charged are calculated as the current Binlog resources minus the free resources.