Tablestore offers two billing modes: VCU mode (formerly known as reserved mode) and CU mode (formerly known as pay-as-you-go mode). This topic describes the billing modes, methods, and recommended use cases for Tablestore.
Video introduction
Billing modes
The following table describes the billing modes of Tablestore.
-
No extra fees are charged for SQL statements. However, operations involved in SQL queries, such as table scans and index queries, consume VCU compute resources in VCU mode (formerly known as reserved mode) and generate read throughput in CU mode (formerly known as pay-as-you-go mode).
-
Cross-region replication traffic fees are incurred only if you use the Global Tables feature. For more information, see Global Tables Metering and Billing.
|
Billing mode |
Description |
|
VCU mode (formerly reserved mode) |
You can purchase reserved VCUs in advance based on resource evaluation results, or enable elastic capacity and pay for consumed computing performance on a pay-as-you-go basis. You can use reserved VCUs and elastic capacity together to save costs.
This mode helps you save on compute resource costs. This mode also lets you control overall resource usage by configuring an upper limit for elastic capacity or disabling elastic capacity. This prevents extra fees caused by unusual traffic. This makes it a better choice for scenarios that require cost control. Note
For more information, see Resource estimation and selection. Billable items include computing power, data storage, cross-region replication traffic, and outbound public traffic, where data storage includes high-performance storage, Capacity storage, and search index storage. For more information, see VCU mode (formerly Reserved mode). |
|
CU mode (formerly pay-as-you-go mode) |
You are charged for resources such as real-time read/write throughput and storage space. You do not need to plan hardware resource consumption in advance. This mode is suitable for scenarios where workloads fluctuate significantly and unpredictably. The elastic capacity provided by CU mode (formerly pay-as-you-go mode) ensures that your application can handle traffic bursts. This makes it a better choice for scenarios that require high service stability. Important
In CU mode (formerly pay-as-you-go mode), you cannot control the upper limit of overall resource usage. You must manage resource usage at the application layer to prevent extra overhead from unusual traffic and usage. Billable items include read throughput, write throughput, data storage, cross-region replication traffic, and outbound public network traffic. For more information, see CU mode (formerly Pay-As-You-Go mode). |
Billing methods
Tablestore supports the following billing methods.
|
Billing method |
Description |
|
Subscription |
|
|
Pay-as-you-go |
|
Note
Resource plans cannot be used to offset fees for Internet traffic. |
Recommended use cases
Select a recommended solution based on your business scenario.
|
Business scenario |
Description |
Recommended solution |
References |
|
Stable and predictable workloads |
The workload does not have significant peaks and valleys, and no unexpected traffic bursts occur. Examples include monitoring and IoT scenarios. |
VCU mode (formerly reserved mode) |
|
|
Workloads with traffic bursts |
The workload has unpredictable traffic bursts. Examples include media assets and news. |
|
|
|
Batch offline tasks |
Low-frequency but large-scale offline data reads and writes are performed at scheduled times every day. |
CU mode (formerly pay-as-you-go mode) and resource plans |
|
|
Business testing |
Set up a staging environment to test the product in the early stages. |
CU mode (formerly pay-as-you-go mode) |
