RDS for MySQL is an elastic and reliable online relational database service for Volcano Engine based on the open-source MySQL database. RDS for MySQL instances are deployed in a cloud-native manner and use local SSD storage to provide high-performance read/write capabilities. They are fully compatible with the MySQL engine and provide a complete set of solutions including instance management, backups, logs, monitoring, and data migration. This helps enterprises simplify complex database management and operation tasks, allowing them to focus more on their core business.
Product architecture
High availability architecture
MySQL provides a one-primary and one-secondary high-availability architecture type. When the primary node fails, it automatically detects and completes a second-level primary-secondary switch without business interruption, ensuring stability. MySQL supports backup capabilities, including data backup and log backup, and enables restore by backup set and by point in time to ensure data reliability.
Cluster architecture
MySQL uses a one-primary, multiple-secondary cluster architecture and supports automatic failover and manual switching. Secondary nodes are accessible, improving read capabilities. Can be scaled out to a maximum of 8 secondary nodes to further expand read capabilities.
Read/write splitting
RDS for MySQL provides a read/write separation architecture with one primary node and multiple read-only nodes. You can add up to 10 read-only nodes to elastically scale out data read capabilities according to your business needs. It supports read/write separation by automatically forwarding read requests to read-only nodes, which offloads the read pressure on the primary node, effectively handling scenarios with high read and low write volumes.
Core components
The primary node is the basic node of a MySQL instance, which provides services to external users. Other components depend on the primary node to function. In a high-availability architecture, the primary node receives all read/write service requests. In a read/write split architecture, the primary node receives all the write requests and a portion of the read requests. The primary node stores the data modification log and syncs the log among nodes.
The secondary node is an important node in the high-availability architecture of a MySQL instance, ensuring the instance's service availability. The secondary node receives logs sent by the primary node and replays them to ensure data consistency between the primary and secondary nodes; in case of primary node failure, the secondary node can quickly switch to the primary node to provide services, ensuring stable business operation.
The read-only node is an important node in the read/write separation architecture of an RDS for MySQL instance, responsible for handling read-only requests. Read-only nodes are an important node of the read/write splitting architecture of a MySQL instance. They receive log files from secondary nodes or the primary node and replay them to ensure data consistency between the read-only nodes and the primary/secondary nodes; in scenarios with more reads and fewer writes, they handle read-only requests and share the data read load of the primary node.
Product features
Product features Powerful hardware to ensure performance
- RDS for MySQL uses NVMe SSDs to provide two storage types: local disk and cloud disk. With the local disk storage type, NVMe SSD's strong IO performance ensures the database's read and write access capabilities, providing high reliability and persistence for data. With the cloud disk storage type, a multiple redundancy mechanism is supported to avoid the risk of a single point of data failure, providing 99.9999999% reliability and offering reliable support for the database. Cloud disks support the end-to-end 16K atomic write feature, which can ensure the atomicity of each data page write, thereby safely disabling the InnoDB doublewrite mechanism. This not only greatly reduces the I/O write volume, but also simplifies the process of flushing dirty pages, thus greatly improving the write performance of MySQL.
tip
A service period is one calendar month. Data persistence = (Total data volume in the service period - Data volume lost in the service period) / Total data volume in the service period * 100%.
High-availability architecture
- It has a high-availability primary/secondary architecture to ensure service availability. Once the primary node suffers a fault, the system automatically detects the fault and completes primary/secondary switchover within seconds.
tip
Product data is saved in two copies in the data center without a cold backup or backups in other data centers.
Read/write splitting
- MySQL supports the mounting of read-only nodes, as well as the one-primary and multi-read-only node architecture, to implement automatic read/write splitting to easily cope with high request volumes.
Backup and recovery
- Based on data backup and log backup (Binlog), RDS for MySQL supports lossless data recovery within 7 days to 12 months to ensure data reliability.
Supports multi-availability zone deployment
- When creating or restoring a new instance, you can assign the primary, standby, and read-only nodes to different availability zones within the same region to enable cross-availability zone disaster recovery.
tip
Currently, restoring a single availability zone instance to a multiple availability zone instance is not supported.
Product advantages
Product advantages Easy management of massive databases
- RDS for MySQL provides two cloud database management methods, namely command line and web interface, and supports batch management of database accounts and permissions.
Backup and recovery
- RDS for MySQL supports data import through DTS. It automatically backs up data every day. The data can be restored to any time point in the log backup retention period.
Professional monitoring and alerting
- Supports multi-dimensional monitoring and custom resource threshold alarms. It provides online query and download capabilities for various logs.
Multiple access methods
- RDS for MySQL supports access through the internet and VPC networks to interconnect cloud databases with data centers, private clouds, and other computing resources.