ApsaraDB MyBase comes in two editions: High-availability Edition and Master-replica Edition. This topic describes High-availability Edition.
High-availability Edition is the standard choice for production workloads. Each deployment includes a primary instance and a secondary instance by default. You can also add up to seven read-only instances, each built on a primary/secondary architecture.
Supported versions
MySQL 8.0
MySQL 5.7
MySQL 5.6
Topology
Features
High availability
Data replicates from the primary instance to the secondary instance in semi-synchronous or asynchronous mode. If the primary instance becomes unavailable, workloads automatically fail over to the secondary instance.
If a read-only instance fails, its secondary instance takes over as the new read-only instance.
Comprehensive functionality
High-availability Edition includes:
| Feature | Description |
|---|---|
| Secondary instance recreation | Rebuild the secondary instance if needed |
| Backup and restoration | Protect and recover data on demand |
| Performance optimization | Monitor and tune database performance |
| Read/write splitting | Route read and write traffic across instances |
| SQL Explorer | Store logs of all executed SQL statements for up to five years, enabling database access auditing and security analysis |
Limits
The primary and secondary instances must be deployed in the same region to maintain replication performance.
FAQ
How do I change the data replication mode?
Change the replication mode in the console. For details, see Change the data replication mode of an ApsaraDB RDS for MySQL instance.