tencent cloud

Feedback

Serverless Service

Last updated: 2022-06-08 15:58:56

    TDSQL-C for MySQL Serverless Edition adopts the serverless architecture for cloud native database services. It is billed based on the actual computing and storage resource usage, so you only need for pay for what you use while enjoying the cloud native technologies of Tencent Cloud.

    Note:

    Only TDSQL-C for MySQL supports Serverless mode.

    Service Features

    • 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 usage which is calculated by second and settled by hour.

    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.

    Billing Modes

    Computing and storage are billed separately: computing is billed by the number of CCUs, while storage is billed by the usage in GB. The billing system calculates the usage by second and settles fees by hour. For detailed prices, see Billing Overview

    CynosDB Compute Unit (CCU) is the computing and billing unit for the Serverless Edition. A CCU is approximately equal to 1 CPU core and 2 GB memory. The number of CCUs used in each billing cycle is the greater of the number of CPU cores used by the database and 1/2 of the memory size.

    You can select the maximum and minimum CCUs your database requires on the purchase page according to your business conditions. You can also change them in the console.

    Service Management

    Pausing service

    • You can enable/disable the auto-pause feature in the console according to your business needs.
    • After this feature is enabled, you need to set the auto-pause time, which is one hour by default. The database will be automatically paused if it has no active connections and CPU usage after this time elapses. After the pause, the computing resources will not be billed, and the storage resources will be billed by the actual usage.
    • If this feature is disabled, the database will keep running. When there are no active connections and CPU usage, the database will be billed based on the minimum CCU you configure. This is suitable for scenarios where your business has a heartbeat connection.
    • You can also manually pause specified databases in the console.
      Note:

      The auto-pause feature of the Serverless architecture is determined by whether there is a user connection. If a service scenario needs to use event_scheduler to trigger SQL periodically, do not enable auto-pause feature.

    Starting service

    You cannot use the features in the console for a paused serverless database. If needed, you can wait until the database is automatically started or manually start it the console.

    When a paused database is accessed, the system will automatically start it in seconds. During the short startup process, the application may receive the following error messages; therefore, the business should have a reconnection mechanism.

    ERROR 9449 (08S01): CynosDB serverless instance is resuming, please try connecting again
    ERROR 2003 (HY000): Can't connect to MySQL server on  'xxxx' (111)
    

    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support