Billable Item | Description | Commercialization Status | Supported Billing Modes |
Compute Node | Compute nodes consist of read-write nodes and read-only nodes. The cost of a compute node depends on the region where the node is located, the node specification, and the usage duration. Attention: The LibraDB engine for read-only instances does not currently support the Serverless billing mode. | Purchase/Usage Billing | Yearly/monthly subscription Pay-as-you-go Serverless |
Storage Space | Storage space refers to the space occupied by data files, index files, log files (such as redo log, undo log, slow log, and error log), and temporary files. Occupied storage space incurs costs. Storage space is divided into primary storage and secondary storage. Currently, Serverless clusters support enabling secondary storage, allowing you to archive data from primary storage to secondary storage to reduce storage costs. For more information about secondary storage, see Secondary Storage. The cost of storage space depends on the data volume and the storage duration. Attention: Data files in primary storage use a three-replica strong consistency model to ensure reliability, with billing based only on the single replica data volume. Secondary storage stores data in Cloud Object Storage (COS) buckets when instances are suspended. The LibraDB engine uses independent storage space and requires independent billing. It does not reuse the shared storage of TDSQL-C for MySQL. |
Purchase/Usage Billing | Yearly/monthly subscription Pay-as-you-go |
Backup storage space | Backup files consume storage space. Backup methods include automatic backup and manual backup, and backup types include log backup and data backup. The space used by all these backup files is included in this billable item. The cost incurred by backup files depends on the storage capacity and the retention duration. | Temporarily free |
Pay-as-you-go
|
Database Audit | TDSQL-C for MySQL provides database audit capabilities, which record database access and SQL statement execution. This helps enterprises control risks and enhances their data security level. You are charged for the database audit feature only after you enable it. |
Purchase/Usage Billing
|
Pay-as-you-go
|
Instance Mode | Billing Mode | Supported Engines | Billing Mode | Applicable Scenarios |
Provisioned resource (pre-allocated with fixed specifications) | Yearly/monthly subscription | TXSQL/LibraDB | Prepaid mode, in which fees are paid when new instances are created. | Suitable for long-term needs with relatively stable traffic volume. The fee is lower compared to pay-as-you-go mode, and the longer the purchase period, the more discounts you get. |
| Pay-as-You-Go | TXSQL/LibraDB | Pay-as-you-go mode, in which you request resources as needed and fees are charged based on actual resource usage. | It is suitable for business senarios with large instantaneous fluctuations in business volume. The instance can be released immediately after use to save costs. |
Serverless | Compute: CCU quantity Storage: GB usage | TXSQL | Compute and storage are independently billed: compute is billed by the number of CCUs, storage is billed by usage in GB, the billing system charges by the second, and settles by the hour. | Suitable for business scenarios with low-frequency and uncertain loads, such as development and testing. Billing is based on usage, with no usage incurring no charges. Note: Serverless starts with the minimum CPU during initialization. It scales down only if there are no requests ten minutes after startup. Therefore, you are billed for a compute node for a minimum of ten minutes after purchase, even if you do not use it. A CCU (TDSQL-C Compute Unit) is the compute billing unit for Serverless. One CCU is approximately equivalent to the compute resources of 1 CPU and 2 GB of memory. The number of CCUs used in each billing cycle is the maximum value between the number of CPU cores used by the database and 1/2 of the memory size. |
| Resource pack | TXSQL | A prepaid resource type, which is divided into compute resource pack and storage resource pack, can be used to deduct the compute and storage resources generated by Serverless clusters. Among them, the storage resource pack can be used to deduct the data volume of secondary storage (a 1 GB-sized storage resource pack can deduct 30 GB of secondary storage data). | Suitable for business scenarios that require flexible management of compute and storage resources and prepaid billing based on actual usage, such as short-term tasks, applications with significant traffic fluctuations, and large-scale data processing. |
피드백