Background
A provisioned resource database instance requires you to estimate the business peak in advance and purchase resources with fixed specifications. When load fluctuations are significant, this approach often faces a dilemma:
Configuring resources based on peak demand leads to significant resource idleness and cost waste during off-peak periods.
Configuring resources based on average demand leads to performance bottlenecks during peak periods, requiring manual configuration changes in response.
The TDSQL Boundless Serverless instance is designed specifically to address this issue. It can automatically adjust computing and storage resources based on real-time business load fluctuations, ensuring that resource usage consistently matches business demands and truly achieving "pay for what you use".
Strengths of Serverless Service
Automatic Scaling to Adapt to Load
Serverless instances feature automatic auto-scaling capabilities:
Vertical elasticity: It continuously monitors node CPU and memory utilization, automatically adjusts node specifications within the user-defined computing power range, and takes effect within minutes. When local resources are sufficient, it performs in-place configuration changes without interrupting connections or affecting business operations. When local resources are insufficient, it performs cross-machine configuration changes, during which connections may experience brief interruptions before automatically recovering.
Automatic disk expansion: The disk automatically expands when its utilization exceeds the threshold, requiring no manual intervention.
Pay-As-You-Go Billing for Cost Optimization
During low-load periods, it automatically scales down to the minimum computing power, incurring only minimal costs.
Compared to provisioned resource instances, businesses with fluctuating loads can achieve significant cost savings.
Complete Distributed Database Capabilities
Serverless instances, built on TDSQL Boundless, provide the full core capabilities of a distributed database:
Complete MySQL-compatible SQL capabilities
Distributed transactions (strong consistency)
Online DDL
Automatic backup
Note:
The following capabilities are not currently supported for Serverless instances:
Multi-AZ Deployment
3-replica mode (only 2 replicas are supported)
Disaster recovery nodes and CDC nodes
Columnar read-only nodes
Applicable Scenarios
Businesses with Load Fluctuations
Businesses such as gaming, e-commerce, and social media exhibit distinct peak and trough cycles. Serverless instances automatically scale out during peak periods to ensure performance and scale in during troughs to reduce costs, with their resource usage curve closely aligning with the business growth curve.
Development and Test Environments
Development and test databases are used infrequently and remain idle most of the time. Serverless instances are billed only for the minimum computing power when idle and automatically scale out when needed, avoiding long-term fixed costs for infrequently used environments.
Cold Start for New Services
During the initial phase of a new business, it is difficult to accurately predict database load. Serverless instances eliminate the need for upfront capacity planning. They automatically scale out as the business grows, preventing performance issues due to insufficient capacity and avoiding cost waste from over-provisioning.
Use Limits
|
Horizontal Elasticity | Automatic horizontal scaling is not supported. |
Multi-AZ deployment | Multi-AZ deployment is not supported. Only single-AZ deployment is supported. |
3-Replica Mode | Three-replica mode is not supported. Only two-replica mode is supported. |
Disaster Recovery/CDC Nodes | Not supported. |
Columnar Read-Only Nodes | Not supported. |
Automatic Start/Stop | Automatic start/stop is not supported. The instance always runs at the minimum compute capacity. |
Backup and Restore | Only backup is supported. Restore is not supported. |
Disk scaling down | Disk shrink is not supported. Only automatic disk expansion is supported. |
Replica Mode Change | The replica mode cannot be changed after creation. Only two-replica mode is supported. |