Starting July 30, 2024, ApsaraDB RDS for MySQL allows you to enable the general-purpose database proxy feature on the ApsaraDB RDS buy page. If you enable the database proxy feature when you create an ApsaraDB RDS for MySQL instance, you can directly connect to the RDS instance by using the database proxy endpoint after the RDS instance is created. This simplifies connection management and improves the availability and security of the RDS instance.
Introduction
A database proxy serves as a network proxy that resides between your database system and your application and forwards all requests from your application. The database proxy feature provides advanced capabilities, such as read/write splitting, persistent connections, transaction splitting, connection pooling, and SSL encryption. For more information, see What are database proxies?
Effective date
July 30, 2024
Billing rules
The general-purpose database proxy feature is provided free of charge.
Applicable scope
Database engine | Instance category | RDS edition | Database engine version | Description |
MySQL | Primary RDS instance | RDS High-availability Edition | MySQL 8.0, MySQL 5.7, and MySQL 5.6 | By default, the general-purpose database proxy feature is disabled. You can manually enable the feature based on your business requirements. |
RDS Cluster Edition | MySQL 8.0 and MySQL 5.7 | By default, the general-purpose database proxy feature is enabled. You can manually disable the feature based on your business requirements. | ||
Read-only RDS instance | RDS Basic Edition | MySQL 8.0, MySQL 5.7, and MySQL 5.6 | By default, the general-purpose database proxy feature is enabled for the primary RDS instance to which the read-only RDS instances are attached. You can manually disable the feature based on your business requirements. | |
RDS High-availability Edition | MySQL 8.0, MySQL 5.7, and MySQL 5.6 |
Scenarios
The primary RDS instance is heavily loaded due to a large number of requests that are encapsulated in transactions.
The primary RDS instance is heavily loaded due to an excessively large number of connections.
Most of your workloads require short-lived connections.
Read/write splitting is required.
Read-only workloads and workloads that need to be isolated are involved.
The capability to prevent transient connections that are caused by O&M operations such as instance switchovers is required.