ApsaraDB RDS is available in the following editions: Basic Edition, High-availability Edition, Cluster Edition, and Enterprise Edition. This topic describes Enterprise Edition.
Enterprise Edition supports the following database engine versions and instance families:
- Database engine versions: MySQL 5.7 and MySQL 8.0
- Instance families: dedicated instance family, including the dedicated host instance types
For performance purposes, you must deploy the three RDS instances of your database system in the same region.
- High reliability
- Enterprise Edition provides enterprise-grade reliability with a recovery point objective (RPO) of 0.
- The three RDS instances of your database system can be deployed in three different data centers of the same city to support cross-zone disaster recovery.
- Comprehensive functionality
Enterprise Edition supports all the features that are provided by ApsaraDB RDS. These features include automatic scaling, backup and restoration, performance optimization, read/write splitting, and SQL Explorer. The SQL Explorer feature is used to log all the SQL statements that are executed within up to five years. Based on the SQL logs, you can trace database access behavior. This ensures the security of important data.
For more information, see Overview of ApsaraDB RDS editions.
- Strong consistency and high availability
The following improvements are made to the database engines of ApsaraDB RDS to increase data consistency and service availability:
- Raft, a distributed consensus algorithm, is used to ensure the reliability and atomicity of switchovers among the RDS instances in your database system.
- Two data replicas and three log replicas are supported. Transaction logs are synchronized from the primary RDS instance to the secondary RDS instance and logger RDS instance. A transaction is committed only after the related logs are written to at least two of the three RDS instances in your database system.
- If you use MySQL 5.7 or MySQL 8.0, the Raft algorithm is used to control the commitment, rollback, and crash recovery of transactions. This ensures data consistency in your database system.
- The secondary RDS instance and the logger RDS instance replay only the transaction logs that have been written into a majority of the three RDS instances in your database system. In addition, parallel replication algorithms at various levels are used to increase replay efficiency. Therefore, you can reduce the recovery time objective (RTO) and ensure service availability. The supported levels are the database, table, logical clock, and WriteSet levels.
Create an RDS instance
For more information about how to create an RDS instance that runs Enterprise Edition, see Create an ApsaraDB RDS for MySQL instance.
Is Enterprise Edition supported for read-only RDS instances?
No, Enterprise Edition is not supported for read-only RDS instances. You can create a read-only RDS instance for a primary RDS instance that runs Enterprise Edition. However, the created read-only RDS instance is based on the high-availability architecture.