ApsaraDB for RDS offers four editions: Basic Edition, High-availability Edition, Cluster Edition, and Enterprise Edition. This topic describes the Enterprise Edition.

The Enterprise Edition is suitable for enterprises. It uses a three-node architecture that consists of one primary instance and two secondary instances. Data is replicated from the primary instance to the secondary instances to ensure data consistency and finance-level reliability.

The Enterprise Edition supports the following database versions and instance families:

  • Database versions: MySQL 5.7 and 8.0
  • Instance families: dedicated instance family and dedicated host instance family


If you are using the Enterprise Edition, your primary and secondary instances must reside in the same region for stable performance.


  • High reliability
    • The Enterprise Edition offers enterprise-level reliability with a Recovery Point Object (RPO) of 0.
    • Your primary and secondary instances can be deployed in three different data centers in the same city to support cross-zone disaster recovery.
  • Comprehensive functionality

    The Enterprise Edition supports comprehensive features, such as automatic scaling, backup and restoration, performance optimization, and read/write splitting. This edition also supports the SQL explorer feature that is used to log all of the SQL statements that are executed within the last 30 days. The SQL explorer feature makes database access traceable and ensures the security of important data.

    For more information, see ApsaraDB for RDS edition overview.


    If you are using MySQL 5.7 or 8.0 with the Enterprise Edition, a free trial edition of the SQL explorer feature is provided.

  • Consistency and availability

    The kernel of ApsaraDB for RDS has been improved to increase consistency and availability in the Enterprise Edition.

    • A distributed consensus algorithm, Raft, is used to ensure the reliability and atomicity of switchovers between your primary and secondary instances.
    • Two data replicas and three log replicas are provided. In addition, transaction logs are synchronized from your primary instance to your two secondary instances. A transaction is committed only after the log is written into at least two of the three instances.
    • In MySQL 5.7 and 8.0, the Raft algorithm is used to control the commitment, rollback, and crash recovery of transactions. This allows you to ensure the consistency of data in your database system.
    • Non-primary instances only replay the transaction logs that have been written into a majority of instances in your database system. In addition, parallel replication algorithms at the database, table, logical clock, and WriteSet levels are used to improve replay efficiency, reduce Recovery Time Objective (RTO), and ensure instance availability.


Does the Enterprise Edition of ApsaraDB for RDS support read-only instances?

No, the Enterprise Edition of ApsaraDB for RDS does not support read-only instances.