On April 1, 2021, Alibaba Cloud stopped the updates and maintenance for the shared proxy feature of ApsaraDB RDS for MySQL. After this date, Alibaba Cloud provides only technical support for the shared proxy feature. If you no longer use the shared proxy feature (namely, you no longer use the read/write splitting feature), you can disable the shared proxy feature. If you still use the shared proxy feature, we recommend that you upgrade the database proxy that is enabled on your primary RDS instance from a shared proxy to a dedicated proxy at your earliest opportunity.
The database proxy resides between your database system and your application. All requests from your application are sent to the database proxy. Then, the database proxy routes the requests to the primary and read-only RDS instances of your database system based on the read weights of these instances to implement read/write splitting and reduce the loads on the primary RDS instance. For more information, see Introduction to database proxies ApsaraDB RDS for MySQL provides two types of database proxies: dedicated proxies and shared proxies. In contrast with shared proxies, dedicated proxies are easy to use and maintain, and provide high availability and high performance. In addition, dedicated proxies support advanced features, such as transaction splitting and connection pool.
This notice applies to all primary RDS instances on which shared proxies are enabled. These instances run MySQL 5.6 or run MySQL 5.7 on RDS High-availability Edition with local SSDs.
You can go to the Database Proxy page of your primary RDS instance and check for the Read/Write Splitting (Shared) tab. If the tab is available, the shared proxy feature is enabled on the RDS instance.
A shared proxy serves more than one primary RDS instance, and these RDS instances may belong to different users. This decreases the stability of your database service due to potential resource competition and isolation issues. Therefore, we recommend that you upgrade the database proxy of your primary RDS instance from a shared proxy to a dedicated proxy. Dedicated proxies outperform shared proxies. For more information about the benefits of dedicated proxies, see the "Benefits" section of this topic.
- Alibaba Cloud provides updates and maintenance for dedicated proxies. However, Alibaba Cloud no longer provides updates and maintenance for shared proxies.
- The stability of shared proxies is no longer guaranteed in the service level agreement (SLA).
We recommend that you upgrade the database proxy of your primary RDS instance from a shared proxy to a dedicated proxy before April 1, 2021. For more information, see Upgrade the database proxy of an ApsaraDB RDS for MySQL instance from a shared proxy to a dedicated proxy.
Fees are charged for dedicated proxies. For more information, see Billing rules for dedicated proxy.
If you upgrade the database proxy of your primary RDS instance from a shared proxy to a dedicated proxy, you can use the dedicated proxy feature free of charge for at least one year. For more information, see Upgrade promotions.
The following table describes the advantages of dedicated proxies over shared proxies.
|Comparison item||Shared proxy||Dedicated proxy|
|Queries per second (QPS)||The QPS cannot be guaranteed. The maximum QPS is 1,000. You cannot increase the QPS by scaling out resources.||The QPS is stable. Each dedicated proxy supports up to 20,000 QPS. In addition, you can increase the QPS by adding proxy instances. A maximum of 60 proxy instances can be enabled for each primary RDS instance.|
|Stability||A number of primary RDS instances that belong to different users compete for resources.||Each primary RDS instance has its own dedicated proxy and does not need to compete with other primary RDS instances for resources.|
|Availability||Each shared proxy works in the single-node architecture. If a shared proxy becomes faulty, it is disconnected.||Each dedicated proxy works in the high-availability architecture. This ensures the availability of your database service.|
|Monitoring||Monitoring is not supported.||You can monitor the CPU utilization of dedicated proxies to identify proxy resource bottlenecks.|
|Read/write splitting||The read/write splitting feature is supported.||The read/write splitting feature is supported.|
|Read/write splitting endpoint||The read/write splitting endpoint is supported. After the read/write splitting feature is disabled, the read/write splitting endpoint is immediately released. In this case, you must modify the endpoint configuration on your application.||The read/write splitting endpoint is supported. To implement read/write splitting by using a dedicated proxy endpoint, you need only to add the dedicated proxy endpoint to your application. If you enable or disable the read/write splitting feature, you do not need to modify the endpoint configuration on your application. The dedicated proxy endpoint remains valid unless you disable the dedicated proxy feature.|
|Advanced features||None.||The following advanced features are provided: