The features for ApsaraDB RDS for MySQL instances that run RDS Enterprise Edition are no longer iterated. Subsequent feature iterations are integrated into PolarDB-X for continuous development.
You can continue to use the existing RDS instances that run RDS Enterprise Edition and obtain the extended support, including long-term technical support and bug fixes.
Migration solutions
If you still use an RDS instance that runs RDS Enterprise Edition, we recommend that you migrate the data of the RDS instance to a PolarDB-X 2.0 Standard Edition instance or an RDS instance that runs RDS Cluster Edition to improve your service experience.
Solution 1: Migrate the data of an RDS instance that runs RDS Enterprise Edition to a PolarDB-X 2.0 Standard Edition instance
Introduction
PolarDB-X 2.0 Standard Edition is fully compatible with all features of RDS Enterprise Edition for ApsaraDB RDS for MySQL and provides financial-grade disaster recovery to ensure zero data loss when a data center failure occurs. PolarDB-X 2.0 Standard Edition also ensures zero recovery point objective (RPO) and delivers better performance and higher cost-effectiveness than native MySQL. For more information, see PolarDB-X 2.0 Standard Edition.
Migration steps
Use the one-click migration feature to migrate the data of an RDS instance that runs RDS Enterprise Edition to a PolarDB-X 2.0 Standard Edition instance. After the migration, the endpoint of the RDS instance is retained. This way, you can switch over your workloads from the RDS instance to the PolarDB-X 2.0 Standard Edition instance without the need to modify the connection settings of your application. For more information, see Upgrade an ApsaraDB RDS for MySQL Enterprise Edition instance to a PolarDB-X 2.0 Standard Edition instance.
You can migrate the data of RDS instances that run MySQL 5.7 and MySQL 8.0 on RDS Enterprise Edition to PolarDB-X 2.0 Standard Edition instances.
PolarDB-X 2.0 Standard Edition instances are available in the following regions:
China (Beijing), China (Hangzhou), China (Hong Kong), China (Qingdao), China (Shanghai), China (Shenzhen), China (Zhangjiakou), Germany (Frankfurt), Indonesia (Jakarta), Singapore, US (Silicon Valley), and US (Virginia)
If you want to create an PolarDB-X 2.0 Standard Edition instance in other regions, submit a ticket.
Solution 2: Migrate the data of an RDS instance that runs RDS Enterprise Edition to an RDS instance that runs RDS Cluster Edition
Introduction
RDS Cluster Edition for ApsaraDB RDS for MySQL uses a high availability (HA) architecture that contains one primary node and multiple secondary nodes and supports compute-storage separation. RDS Cluster Edition for ApsaraDB RDS for MySQL is fully compatible with all features of RDS Enterprise Edition for ApsaraDB RDS for MySQL. In RDS Cluster Edition, secondary nodes are readable, up to eight secondary nodes can be created, and the MySQL group replication (MGR) mode is supported to ensure zero RPO. An RDS instance that runs RDS Cluster Edition is referred to as an RDS cluster. For more information, see RDS Cluster Edition.
Migration steps
Manually migrate the data of your RDS instance that runs RDS Enterprise Edition to an RDS instance that runs RDS Cluster Edition. RDS Cluster Edition for ApsaraDB RDS for MySQL is fully compatible with all features of RDS Enterprise Edition for ApsaraDB RDS for MySQL. For more information, see Migrate data from an ApsaraDB RDS for MySQL Enterprise Edition instance to an ApsaraDB RDS for MySQL Cluster Edition instance.
You can migrate the data of RDS instances that run MySQL 5.7 and MySQL 8.0 on RDS Enterprise Edition to RDS instances that run RDS Cluster Edition.
RDS instances that run RDS Cluster Edition are supported in all regions except for Middle East regions.