How Tablestore is billed - Tablestore - Alibaba Cloud Documentation Center

You are charged for each Tablestore instance. This topic describes the pricing and billable items of Tablestore.

Pricing

For more information about pricing, see the Tablestore product page.

Billing method

Tablestore uses the pay-as-you-go billing method. This is a postpaid method, which means you are charged on an hourly basis after you create a table.

Important

The pay-as-you-go billing method does not allow you to set a limit on your overall resource usage. You must manage resource usage at the application layer to prevent extra overhead from unusual traffic or usage.

Billable items

The fees for a Tablestore instance consist of the following billable items:

Billable item		Billing rule
Data storage		The average of the total data volume of an instance per hour in a billing cycle.
Read throughput	Reserved read throughput	The sum of the reserved read throughput of all tables in an instance. You are charged based on the average reserved read throughput per hour in a billing cycle. Note Only high-performance instances support reserved read throughput. For more information about instances, see Instance.
Read throughput	Pay-as-you-go read throughput	The actual read throughput consumed per second. Tablestore charges you for the sum of the pay-as-you-go read throughput of all tables in an instance within a billing cycle.
Write throughput	Reserved write throughput	The sum of the reserved write throughput of all tables in an instance. You are charged based on the average reserved write throughput per hour in a billing cycle. Note Only high-performance instances support reserved write throughput. For more information about instances, see Instances.
Write throughput	Pay-as-you-go write throughput	The actual write throughput consumed per second. Tablestore charges you for the sum of the pay-as-you-go write throughput of all tables in an instance within a billing cycle.
Cross-region replication traffic	Pay-as-you-go	When you use global tables, cross-region data transfer traffic is generated during asynchronous data replication to each replica table. You are charged based on the actual volume of synchronized data, in GB. Important The cross-region replication traffic fees for each replica are calculated separately. The fees are billed to the instance from which data is pulled.
Outbound Internet traffic		The fees for outbound Internet traffic that is generated when an application accesses Tablestore. This traffic is mainly the responses that are returned when the application accesses Tablestore over HTTP. Formula: Fees for outbound Internet traffic = Outbound Internet traffic (GB) × Unit price per GB. Note Tablestore charges you only for outbound Internet traffic. Inbound traffic and traffic over the internal network are free of charge. If an access request fails, Tablestore returns a failure message. This also generates outbound traffic. Access between different regions is also considered Internet access.

Billing rules for core features

You are charged when you use core features such as search index, secondary index, SQL query, time series model, multiple data versions, lifecycle management, Tunnel Service, and data migration and synchronization. The following table describes the billing rules for each feature.

Important

If you access Tablestore over the Internet, you are charged for outbound Internet traffic.
No extra fees are charged for SQL statements. However, you are charged for the operations involved in SQL queries, such as table scans and index queries.

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	The computation for SQL statements does not consume read or write throughput. However, when you execute SQL statements to query data, operations such as table scans and index-based queries consume read and write throughput. For more information, see Billable items of SQL query.
Secondary index	Billable items include data storage and read throughput for the secondary index. For more information, see Billable items of secondary indexes.
Time series model	Billable items include storage usage, and metered read and write throughput. For more information, see Billable items of the TimeSeries model.
Multiple data versions	You are charged for the storage used by multiple data versions and their version numbers. For more information, see Data storage.
Lifecycle management	You are not charged for data cleanup when using lifecycle management. However, enabling the lifecycle management feature adds timestamps as version numbers to each attribute column, which consumes additional storage. For more information, see Data storage.
Tunnel Service	The Tunnel Service feature is free of charge. When you consume data from Tunnel Service, you are charged for read throughput based on the actual amount of data that is pulled.
Global tables	The data read/write and data storage fees for a global table vary based on the data table type. You are also charged for cross-region replication traffic. For more information, see Global Table Metering and Billing.
Data synchronization and migration (using tools or other products)	If you use migration tools or other products, such as Data Transmission Service (DTS), to synchronize or migrate Tablestore data, you are charged for read and write throughput based on the actual read and write requests.
Access from compute engines (MaxCompute, Spark, Flink, and others)	If you use compute engines to access Tablestore, you are charged for read and write throughput based on the read and write requests that are made.