RDS MySQL editions and their use cases - ApsaraDB RDS - Alibaba Cloud Documentation Center

Compare ApsaraDB RDS for MySQL editions by architecture, use cases, and supported features.

ApsaraDB RDS for MySQL editions

Edition	Description	Use cases
Basic Edition	Single-node architecture with separated compute and storage. Does not support read-only instances.	Personal learning. Small-scale websites. Dev/test environments for small and medium businesses.
RDS High-availability Edition	One primary and one secondary node with automatic failover. The secondary node is not accessible. Supports read-only instances for read scaling.	Production databases for medium and large enterprises. Internet, IoT, retail e-commerce, logistics, and gaming workloads.
Cluster Edition	One primary and multiple secondary nodes with automatic failover. Secondary nodes are readable. Add more secondary nodes for additional read scaling.	Production databases for medium and large enterprises. New retail, automotive manufacturing, and large-scale ERP workloads.

Upgrade from Basic Edition to RDS High-availability Edition: Available for instances running MySQL 5.7, 8.0, or 8.4.
Upgrade from Basic Edition to Cluster Edition: Requires cloud disks. Available for instances running MySQL 5.7, 8.0, or 8.4.
Upgrade from RDS High-availability Edition to Cluster Edition: Requires cloud disks. Available for instances running MySQL 5.7, 8.0, or 8.4.
Downgrading from High-availability Edition to Basic Edition, or from Cluster Edition to High-availability or Basic Edition is not directly supported. To downgrade, create a new instance and migrate data from the original instance to the new instance.

Check the edition on the Basic Information page of your instance.