TencentDB for MySQL Cluster Edition
Last updated: 2025-11-11 10:21:53
TencentDB for MySQL supports four types of architectures: single-node, dual-node, three-node, and cluster edition. This document introduces the cluster edition architecture.
Note:
The TencentDB for MySQL cluster edition (cloud disk edition) employs a one-primary-many-standby pattern, where the primary node (read-write node) provides access services, and 1 to 5 standby nodes (read-only nodes) offer read-only access.
The cluster edition features compute and storage separation in a one-primary-many-standby architecture, supports automatic failover, any standby node (read-only node) can switch to become the primary node (read-write node), standby nodes are readable, allows on-demand node addition and deletion, multi-AZ disaster recovery, node-level monitoring, cluster node topology management, etc. It is more economical, flexible, and reliable compared to self-built databases.
The Cluster Edition architecture can be divided into standard, enhanced, and flagship editions based on different isolation policies. See Isolation Policies.
Applicable Scenario
They are widely used in a variety of industries, including gaming, the internet, IoT, retail, e-commerce, logistics, insurance, and securities.
Architecture characteristics
The computing resource is not bound to the disk specification, allowing for high flexibility and fuller resource utilization.
Disk types of all performance levels are supported, including Tremendous SSD, Enhanced SSD, Premium Disk, and Cloud SSD.
Backup uses the form of cloud disk snapshots. The speed of backup and recovery is extremely fast, satisfying the needs for instant rollback.
Supports rapid node addition and deletion. Based on business needs, read-only nodes can be quickly added or removed, with each read-only node capable of being deployed in its own availability zone. This adapts to business requirements while ensuring high availability and disaster recovery capability.
Supports standby node read-only functionality. Traditional backup databases only provide disaster recovery without access. All standby nodes (read-only nodes) in cluster edition instances have their own read-only addresses, and there's no need to create inaccessible standby machines.
There are two primary-backup replication modes: asynchronous and semi-sync (default). The replication mode can be modified on the console's instance details page.
Features are comprehensive, including standby database read-only, rapid addition/removal of read-only nodes, node-level monitoring, and multi-availability zone disaster recovery, among others.
Cluster edition instances can achieve an availability of 99.95%
Cluster edition instances utilize multiple replicas to ensure data storage durability. Data produced by read/write nodes will be synchronized to other read-only nodes, effectively ensuring data security and achieving a data storage durability of no less than 99.9999999%.
Basic Framework Diagram of the Architecture
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback