The provision of the first enabled dedicated proxy free of charge is ended on August 31, 2020. Since September 1, 2020, you are charged for every dedicated proxy that you enable on your RDS instance. The processing capabilities of dedicated proxies are enhanced. In normal cases, each dedicated proxy can process up to 20,000 requests per second.

Effective date

August 31, 2020

Description

  • The provision of the first dedicated proxy free of charge is ended. You are now charged for every dedicated proxy that you enable on your RDS instance.
  • The processing capabilities of dedicated proxies are enhanced. In normal cases, each dedicated proxy can process up to 20,000 requests per second.
Note The discounts that are provided for the upgrade from shared proxy to dedicated proxy remain unchanged. For more information, see Upgrade an ApsaraDB RDS for MySQL instance from shared proxy to dedicated proxy.

Billing

Dedicated proxies are billed on a pay-as-you-go basis. For more information about the prices, see What are dedicated proxies?

Introduction to dedicated proxies

ApsaraDB RDS for MySQL provides two types of database proxies: dedicated proxies and shared proxies. A database proxy resides between a database system and an application. The database proxy receives requests from the application and routes the requests to the primary RDS instance and read-only RDS instances in the database system. The database proxy is easy to use and maintain and provides high availability and high performance. The dedicated proxy also provides advanced features, such as automatic read/write splitting, transaction splitting, and connection pooling.
Note Only dedicated proxies are supported. For more information, see What are database proxies?.

A dedicated proxy is also called a single-tenant proxy. A dedicated proxy allows your database system to use dedicated proxy computing resources. Therefore, a dedicated proxy has the following benefits over a shared proxy:

  • The dedicated proxy provides higher stability.
  • The dedicated proxy provides higher isolation.
  • The dedicated proxy provides better performance. A maximum of 60 proxy instances can be created for each RDS instance. A SysBench test shows that each proxy instance supports 20,000 to 50,000 queries per second (QPS) in online transaction processing (OLTP) scenarios. We recommend that you estimate the maximum QPS that is supported by your RDS instance based on your actual stress test results.
    Note The maximum number of connections to the dedicated proxy is not limited. This number varies based on the specifications of the primary and read-only RDS instances in your database system.
  • The dedicated proxy supports scaling. You can increase the number of proxy instances based on your business requirements. For more information, see Adjust the number of dedicated proxies on an ApsaraDB RDS for MySQL instance.
  • The dedicated proxy supports performance monitoring. You can adjust the number of proxy instances based on the monitoring data and your business planning. For more information, see View the monitoring data of dedicated proxies on an ApsaraDB RDS for MySQL instance.
  • If you change the network type of a primary RDS instance, the network type of the read/write splitting endpoint remains unchanged. For more information, see Change the network type of an ApsaraDB RDS for MySQL instance and What is read/write splitting?.
  • A unified proxy endpoint is provided. This eliminates the need to modify the endpoint information on your application and reduces maintenance costs. The proxy endpoint remains valid until you release the proxy instances. For more information, see Manage the dedicated proxy endpoints of an ApsaraDB RDS for MySQL instance. The proxy endpoint remains connected unless you release the enabled proxy instances. For example, you may enable the read/write splitting feature during peak hours, and then release read-only RDS instances and disable the read/write splitting feature during off-peak hours. In these cases, the proxy endpoint remains connected, and you do not need to update the endpoint information on your application.
  • The dedicated proxy supports automatic read/write splitting. This reduces maintenance costs. For more information, see Enable the read/write splitting feature for an ApsaraDB RDS for MySQL instance. In normal cases, to implement read/write splitting, you must manually add the endpoints of the primary and read-only RDS instances to your application. This applies if the read-only RDS instances are available. If you enable the dedicated proxy feature, you need to add only a unified proxy endpoint to your application. This way, all the requests from your application are sent to the proxy endpoint. Then, the proxy endpoint routes read requests to the read-only RDS instances and write requests to the primary RDS instance based on the read weights of these instances. You do not need to update the configuration data on your application even if you create more read-only RDS instances or if you delete existing read-only RDS instances.
  • The dedicated proxy provides more advanced features, such as connection pool and transaction splitting. For more information, see Set the connection pool type of an ApsaraDB RDS for MySQL instance and Enable the transaction splitting feature for an ApsaraDB RDS for MySQL instance

For more information, see What are database proxies?