You are charged for resources of each Tablestore instance. This topic describes the pricing, billing method, and billable items of Tablestore.
Pricing
- For information about the pricing of Tablestore, see the Pricing tab of the Tablestore product page.
Billing method
You are charged based on the pay-as-you-go billing method when you use Tablestore resources. This billing method indicates that you are charged for the Tablestore resources that you used on an hourly basis.
Billable items
The following table describes the billable items of Tablestore.
Billable item | Description | |
---|---|---|
Storage usage | The average of total data size in each hour of a billing cycle. | |
Read throughput | Reserved read throughput | The average of reserved read throughput in each hour of a billing cycle. Note Only high-performance instances support reserved read throughput. For more information about instances, see Instance. |
Metered read throughput | The average of metered read throughput in each hour of a billing cycle. Tablestore calculates the metered read throughput at an interval of 1 second in an hour and uses the metered read throughput that is obtained to calculate the average of metered read throughput in the hour. | |
Write throughput | Reserved write throughput | The average of reserved write throughput in each hour of a billing cycle. Note Only high-performance instances support reserved write throughput. For more information about instances, see Instance. |
Metered write throughput | The average of metered write throughput in each hour of a billing cycle. Tablestore calculates the metered write throughput at an interval of 1 second in an hour and uses the metered write throughput that is obtained to calculate the average of metered write throughput in the hour. | |
Outbound traffic over the Internet | The total Internet outbound traffic that is generated when applications access Tablestore by using HTTP methods. Note
|
Billing rules for core features
Core feature | Billing rule |
---|---|
Search index | You are charged for high-performance storage usage, reserved read throughput, and metered read throughput when you use the search index feature regardless of the instance type. For more information, see Billable items of search indexes. |
SQL query | Computing in SQL statements does not consume read and write throughput. However, when you execute SQL statements to query data, operations such as data table scanning and index-based queries consume read and write throughput. For more information, see Billable items of SQL query. |
Secondary index | The billable items include the storage usage, read and write throughput that is consumed when you create a secondary index, and read and write throughput that is consumed when you perform read and write operations on the secondary index. For more information, see Billable items of secondary indexes. |
TimeSeries model | The billable items include the storage usage and the metered read and write throughput. For more information, see Billable items of the TimeSeries model. |
Max versions | You are charged for the storage usage of version numbers and data with various version numbers. For more information, see Storage usage. |
TTL | When you configure TTL to delete data, you are not charged for the delete operations that are performed by Tablestore. When you enable the TTL feature, Tablestore adds timestamps to each attribute column as the version numbers. You are charged for the storage usage of version numbers and data with various version numbers. For more information, see Storage usage. |
Tunnel Service | You are not charged for Tunnel Service. However, you are charged for the read throughput that is consumed when data in tunnels is consumed. |
Data synchronization and migration by using tools or other services | When you use migration tools or other services, such as Data Transmission Service (DTS) and Alibaba Cloud IoT Platform, to migrate data from Tablestore, you are charged for the metered read and write throughput that is consumed by read and write requests. |
Access from compute engines such as MaxCompute, Spark, and Flink | You are charged for the metered read and write throughput that is consumed by read and write requests when you use compute engines to access Tablestore. |