RDS for MySQL Product Series
Table 1 and Table 2 list different DB instance types and their function comparisons of RDS for MySQL.
| DB Instance Type | Description | Notes | Advantages | Scenarios |
|---|---|---|---|---|
| Single | A single-node architecture is more cost-effective than a primary/standby DB pair. | If the node fails, the restoration will take a long time. Therefore, single-node instances are not recommended for sensitive workloads that have high requirements on database availability. | Different from primary/standby DB instances that have two database nodes, a single DB instance has only one node. |
|
| Primary/Standby | An HA architecture. A pair of primary and standby DB instances shares the same IP address. |
| An HA architecture improves database reliability. If the primary node fails, the standby node attempts to become the primary node to reduce the impact on workloads. |
|
| Function | Single | Primary/Standby |
|---|---|---|
| Number of nodes | 1 | 2 |
| Specifications | vCPUs: a maximum of 64 Memory: a maximum of 256 GB Storage: a maximum of 4,000 GB Final specifications on the console may differ slightly. | vCPUs: a maximum of 64 Memory: a maximum of 256 GB Storage: a maximum of 4,000 GB Final specifications on the console may differ slightly. |
| Monitoring and alarms | Supported | Supported |
| Security group | Supported | Supported |
| Backup and restoration | Supported | Supported |
| Parameter settings | Supported | Supported |
| SSL | Supported | Supported |
| Log management | Supported | Supported |
| Read replicas (which need to be created) | Supported | Supported |
| Read/write splitting | Supported | Supported |
| SQL audit | Supported | Supported |
| Monitoring by Seconds | Supported | Supported |
| Failover | Not supported | Supported |
| Manual primary/standby switchover | Not supported | Supported |
| Instance class change | Supported | Supported |
| Storage scale-up | Supported | Supported |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.