Overview of MySQL Cloud Disk Edition
Download
Focus Mode
Font Size
TencentDB for MySQL supports the cloud disk edition product architecture, featuring high elasticity, high performance, flexibility, and security and reliability, while also leveraging the advantages of open-source cloud databases, such as simplicity, openness, and efficient iteration. It provides multiple capabilities unique to the cloud disk edition, including: automatic failover, switching any replica node (read-only node) to a primary node (read-write node), read-only replica nodes, on-demand node addition and deletion, multi-AZ disaster recovery, node-level monitoring, and node topology management. This helps users handle diverse and complex business scenarios, enabling them to meet various business requirements with a single database.
What Is the Cloud Disk Edition?
The Cloud Disk Edition is a cloud-native high-availability deployment model featuring multiple readable replica database nodes. The Cloud Disk Edition provides both read-write access addresses and read-only access addresses. For dual-node/three-node instances, the secondary database only offers high availability and does not provide access. From a performance and cost perspective, the architecture deployment model of the Cloud Disk Edition is suitable for more complex business scenarios, such as business systems with frequent changes, large database volumes, high read performance requirements, and needs for frequent specification adjustment or addition/deletion of read-only instances.
MySQL Cloud Disk Edition supports both asynchronous replication and semi-sync replication. The replication mode can be selected on the purchase page and modified later in the instance details page within the console. To learn more about replication modes, see Database Instance Replication.
The storage type of MySQL Cloud Disk Edition is cloud disk, supporting Extreme SSD CBS, Enhanced SSD CBS, and SSD CBS. The cloud disk type can only be selected on the purchase page. For detailed performance of each CBS, see CBS Types.
Architecture Diagram
Architecture Application
Users can freely deploy the number of primary/secondary nodes based on actual business needs to achieve the most suitable database deployment method for operational requirements, optimizing both cost and performance.
For example, the following are several common deployment scenarios (representing only some scenarios).
One primary and one secondary: The read-write node handles online business, while the read-only node serves as failover preparation and processes lightweight read requests. This deployment is suitable for production environments with moderate availability requirements.
One primary and two secondaries: The read-write node handles online business, read-only node 1 serves online analytical business for data reading, and read-only node 2 provides failover preparation. This deployment is suitable for scenarios requiring high availability while also providing enhanced flexibility and availability.
One primary and multiple secondaries: The read-write node handles online business, while multiple read-only nodes distribute the load of read requests, providing higher read request-handling capacity. This deployment is suitable for businesses with high read request demands.
Strength
Performance Improvements: Multiple kernel optimizations, such as atomic writes, code segment optimization, and Buffer Pool warm-up, have resulted in significant performance gains.
Secondary nodes are read-only: The secondary database supports configuring read-only addresses without creating an inaccessible secondary server.
High Elasticity: Specifications can be quickly adjusted and scaled out based on business needs to optimize costs for computing resources.
Flexibility: Read-only nodes can be quickly added or removed based on business needs. A cloud disk edition instance supports adding or removing 1 to 5 read-only nodes.
Secure and Reliable: Supports both async replication and semi-sync replication. By deploying multiple replica nodes, the solution ensures business continuity while maintaining source-replica synchronization.
Billing
To learn about the billing methods and items for TencentDB for MySQL cloud disk edition, see Billing Overview.
To learn about the pricing for TencentDB for MySQL cloud disk edition, see Price Calculator.
To learn about the free storage space and backup billing beyond the free tier for TencentDB for MySQL cloud disk edition, see Backup Space Billing.
Supported Features
MySQL cloud disk edition instances support features that are largely the same as those of two-node/three-node MySQL instances. For a detailed feature comparison, see Product Features.
For the differences in features and operations between MySQL cloud disk edition instances and two-node/three-node MySQL instances, see subsequent articles in this section.
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback