This document introduces the features and applicable scenarios of the TDSQL-C for MySQL database proxy service.
A database proxy is a network proxy service located between the cloud database service and the application service. It is used to proxy all requests when the application service accesses the database.
The database proxy access address is independent of the original database access address. Requests made through the database proxy address are all relayed through the proxy cluster to access the primary/secondary nodes of the database, handle read-write separation, and forward read requests to read-only instances, thereby reducing the load on the primary databases.
Note:
The database proxy is currently in open beta, and support for regions is being rolled out gradually. If the region where your cluster is located does not yet have the database proxy option, meaning it is not yet available, we apologize for any inconvenience.
Database Proxy Features
High Stability
It is deployed with a cluster architecture, and multiple nodes ensure smooth failover.
Strong Isolation
The database proxy uses dedicated resources to provide proxy services for the current instance (each proxy's resources are independent and not shared).
Ultra-High Performance
Each proxy can handle up to approximately 100,000 requests per second.
Easy and Fast Scaling
It supports dynamic scaling from 1 to 60 proxy nodes (with a maximum of 4 nodes supported during the open beta).
Comprehensive Performance Monitoring
It provides second-level monitoring of performance metrics such as read/write request counts, CPU, and memory. You can adjust the number of proxies based on monitoring data and business planning. Hot Reloading
When events such as primary instance failover, configuration adjustment, or addition/removal of read-only instances occur, the database proxy can dynamically hot-reload its configuration without causing network interruption or requiring a restart.
Supports Automatic Read-Write Splitting
Enabling the read-write splitting feature of the database proxy can effectively reduce the read load on the primary instance. It provides horizontal scaling capability for the database cluster by adding read-only instances, helps users achieve self-service read-write splitting, and reduces the complexity of users manually splitting business read and write requests. This is particularly suitable for scenarios with heavy read loads.
After the read-write splitting feature of the database proxy is enabled, you only need to configure one proxy connection address in your application. This address automatically implements read-write splitting, sending read requests to read-only instances and write requests to the primary instance. Even if you add or remove read-only instances, no adjustments to the application settings are required. Use Cases
For businesses dominated by a large number of short-lived connections, performance is insufficient.
When a business uses multiple read-only instances and manually implements read-write splitting at the application side, the maintenance cost and risk are high.
An excessive number of connections causes high instance load.