tencent cloud

TencentDB for MySQL

Database Instance Types

Download
Focus Mode
Font Size
Last updated: 2026-11-06 20:42:31
AI-Translated
A TencentDB for MySQL instance, or simply an instance, is a database environment that runs independently in Tencent Cloud. It is the basic unit for purchasing the TencentDB for MySQL service. Users can create, modify, and delete TencentDB for MySQL instances through the console. Instances are independent of each other with isolated resources, so there are no resource contention issues such as CPU, memory, or IO between them. Each instance has its own characteristics, such as database type and version, and the system has corresponding parameters to control instance behavior.
TencentDB for MySQL offers the following types of database instances:
Instance Type
Definition
Architecture
Visible in Instance List or Not
Function
Primary Instance
Instance that can read and write
Yes
A primary instance can mount read-only instances and disaster recovery instances to implement read-write separation and remote disaster recovery. The single-node architecture does not support mounting read-only instances or disaster recovery instances.
Read-Only Instance
Read-only instance that uses the TXSQL kernel
Yes
A read-only instance cannot exist independently. It must belong to a primary instance, and its only data source is data synchronized from the primary instance.
Read-only analysis engine instance
A type of read-only instance that uses the LibraDB kernel
Single-Node
Yes
A read-only analysis engine cannot exist independently. It must belong to a primary instance, and its only data source is data synchronized from the primary instance. It can only be in the same region as the primary instance. It uses the LibraDB kernel as a columnar storage replica.
Disaster recovery instance
Instance that provides cross-AZ and cross-region disaster recovery capabilities
Yes
A disaster recovery instance is read-only during synchronization. It can actively disconnect the synchronization relationship with the primary instance and promote itself to a primary instance to provide read and write access. It is recommended to deploy the disaster recovery instance in a different region from the primary instance.

Related Information

For operations and precautions related to creating read-only instances, see Creating Read-Only Instances.
For operations on adding or deleting read-only nodes in the cloud disk edition, see Adding Instance Nodes and Deleting Instance Nodes.
For creating and configuring read-only instance RO groups, see Managing Read-Only Instances.
For operations and precautions related to creating disaster recovery instances, see Managing Disaster Recovery Instances.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback