On this page

Show all

Help Center/ Relational Database Service/ Service Overview/ Product Series/ RDS for MySQL Product Series

RDS for MySQL Product Series

Updated on 2025-03-19 GMT+08:00

View PDF

Table 1 and Table 2 list different DB instance types and their function comparisons of RDS for MySQL.

**Table 1** DB instance types
DB Instance Type	Description	Notes	Advantages	Scenarios
Single	A single-node architecture is more cost-effective than a primary/standby DB pair.	If a fault occurs on a single instance, the instance cannot recover in a timely manner.	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.	Personal learning Microsites Development and testing environment of small- and medium-sized enterprises
Primary/Standby	An HA architecture. A pair of primary and standby DB instances shares the same IP address.	When a primary instance is being created, a standby instance is provisioned synchronously to provide data redundancy. The standby instance is invisible to you after being created. If the primary instance fails, a failover occurs, during which database connection is interrupted. If there is a replication delay between the primary and standby instances, the failover takes an extended period of time. The client needs to be able to reconnect to the instance.	The standby node of a primary/standby DB instance is only used for failover and restoration. It does not provide services. The performance of single DB instances is similar to or even higher than primary/standby DB instances because standby nodes cause extra performance overhead.	Production databases of large and medium enterprises Applications for the Internet, Internet of Things (IoT), retail e-commerce sales, logistics, gaming, and other industries

**Table 2** Function comparisons
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

Parent topic: Product Series

Previous topic: Product Series

Next topic: RDS for MariaDB Product Series

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback