TDSQL-C for MySQL Serverless adopts Tencent Cloud's proprietary serverless architecture for next-gen cloud-native relational database services. It is billed based on the actual computing and storage resource usage, so you only need to pay for what you use while benefiting from Tencent Cloud native technologies.
Background
In modern enterprises, databases play a critical role in IT systems. When a database is created, it is essential to carefully configure database cluster resources, including CPU, memory, storage, and various parameters, to ensure smooth business operations during both peak and off-peak periods. However, traditional resource allocation methods often come with inherent drawbacks: During off-peak periods, cluster resources remain idle, leading to wasted resources, while during peak periods, resource shortages may occur, affecting system performance.
The Serverless service effectively addresses this issue by enabling database cluster resources to scale dynamically based on business loads. This eliminates the need for Ops personnel to perform complex resource evaluation and management, significantly reducing their workload.
TDSQL-C for MySQL is divided into provisioned resource clusters and Serverless clusters based on instance mode. In scenarios with significant business fluctuations, a Serverless cluster can efficiently handle low-load periods and traffic spikes while also reducing overall business costs.
Provisioned resource cluster: Due to fixed specifications, if timely configuration adjustments are not made, it is easy to waste resources during service downtime and face resource shortages during peak periods.
Serverless cluster: Since it allows precise control over resource scaling limits, continuously monitors workload metrics such as CPU and memory usage, and triggers automatic scaling policies based on predefined rules. Additionally, it supports automatic start and stop and elastic anti-jitter capabilities. As a result, using a Serverless cluster improves resource utilization and reduces costs.
Autopilot: The database can automatically start/stop according to the business load and scale in an imperceptible manner without causing disconnections.
Utility pricing: The database is billed based on the actual computing and storage resource usage. Computing fees are charged based on the number of CCUs, and storage fees are charged based on the amount of storage used (GB). The billing system is calculated per second and settled hourly.
Use cases
Low-frequency database usage scenarios such as development and test environments.
Scenarios where the load is uncertain, such as IoT and edge computing.
SaaS application scenarios such as Mini Program Cloud Base and SME website development.
Education scenarios such as experiment and teaching environment.
Fully managed and Ops-free scenarios.
Business scenarios with uncertain and intermittent fluctuations.
