Function Comparison
Single DB instances use a single-node architecture. Different from the primary/standby DB instances, a single DB instance contains only one node and has no slave node for fault recovery.
Advantage Comparison
- Single DB instances: support the creation of read replicas and support the queries of error logs and slow query logs. Different from primary/standby DB instances that have two database nodes, a single DB instance has only one node. If the node fails, the restoration will take a long time. Therefore, single DB instances are not recommended for sensitive services that have high requirements on database availability.
- Primary/Standby DB instances: use the slave database node only for failover and restoration. The slave database node does not provide services. The performance of single DB instances is similar to or even higher than the primary/standby DB instances.
Function |
Single |
Primary/Standby |
---|---|---|
Number of nodes |
1 |
2 |
Specifications |
vCPUs: a maximum of 32 Memory: a maximum of 128 GB Storage: a maximum of 4,000 GB |
vCPUs: a maximum of 32 Memory: a maximum of 128 GB Storage: a maximum of 4,000 GB |
Monitoring and alarms |
Supported |
Supported |
Security group |
Supported |
Supported |
Backups and restorations |
Supported |
Supported |
Parameter settings |
Supported |
Supported |
SSL |
Supported |
Supported |
Log management |
Supported |
Supported |
Read replicas (need to be created) |
Supported |
Supported |
High-frequency monitoring |
Supported |
Supported |
Primary/standby switchover or failover |
Not supported |
Supported |
Standby DB instance migration |
Not supported |
Supported |
Manual primary/standby switchover |
Not supported |
Supported |
Instance class change |
Supported |
Supported |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot