Starting July 30, 2024, ApsaraDB RDS for MySQL supports enabling the general-purpose database proxy on the buy page at instance creation time. After the instance is created, connect directly through the proxy endpoint. This simplifies connection management and improves instance availability and security.
Database proxy
A database proxy sits between your application and your database and forwards all requests from your application. It provides:
-
Read/write splitting — route read queries to read-only instances automatically
-
Connection pooling — maintain a smaller pool of long-lived database connections while supporting a large number of application connections
-
Persistent connections — keep connections alive across short-lived application requests
-
Transaction splitting — split transactions for more efficient resource use
-
SSL encryption — encrypt traffic between your application and database
For a full overview, see What are database proxies?
Effective date
July 30, 2024
Billing
The general-purpose database proxy is free of charge.
Supported configurations
| Database engine | Instance category | RDS edition | Supported versions | Default state |
|---|---|---|---|---|
| MySQL | Primary RDS instance | RDS High-availability Edition | MySQL 8.0, MySQL 5.7, MySQL 5.6 | Off — enable manually |
| RDS Cluster Edition | MySQL 8.0, MySQL 5.7 | On — disable manually if needed | ||
| Read-only RDS instance | RDS Basic Edition | MySQL 8.0, MySQL 5.7, MySQL 5.6 | On for the primary instance — disable manually if needed | |
| RDS High-availability Edition | MySQL 8.0, MySQL 5.7, MySQL 5.6 |
When to enable the database proxy
Enable the database proxy when your instance shows any of the following symptoms:
-
The primary RDS instance is heavily loaded due to a large volume of requests encapsulated in transactions.
-
The primary RDS instance is under pressure from an excessive number of concurrent connections.
-
Most workloads use short-lived connections that open and close frequently.
-
Read/write splitting is required to offload read traffic from the primary instance.
-
Read-only workloads must be isolated from write-heavy workloads.
-
Instance switchovers or other O&M operations are causing transient connection drops for applications.