Overview

The RDS proxy instance may automatically allocate the database requests to master instance and read-only instance it is bound to according to read-write type, realizing automated read/write splitting. You can set "Enable Read Traffic Undertaking Feature (Yes/No)" for bound master instance and read-only instance on the Cluster Managemen page in the proxy instance, and simultaneously set specific read traffic allocation weights. Also, current proxy instance is automatically released if current master instance is released.

Notes

• Create master instance before creating proxy instance.
• Proxy instance keeps consistent with master instance in version and region.
• Proxy instance only supports “Postpaid” rather than “Prepaid”, and its billing mode may differ from the master instance’s.
• One proxy instance may be created for one master instance at most.
• See Proxy Instance for detailed creation and management of Proxy Instance.

Architecture diagram

See the diagram. The proxy instance may allocate the server’s read requests to master instance and Read-only Instance, to alleviate the master instance’s pressure in disposal of massive read requests.

Applicable scenarios

Proxy instance needs to be used synchronously with the bound master instance and read-only instance, to realize read/write splitting between master instance and read-only instance in case of massive read requests. Main scenarios include website and Internet, etc.

Support the database engine

Presently, tje RDS for MySQL supports creation of proxy instance (MySQL 5.6 and MySQL 5.7 supported)

Supported regions

North China-Beijing, North China -Baoding, East China-Suzhou, South China-Guangzhou, Financial East China -Shanghai, Financial Central China-Wuhan, Hong Kong, and Singapore.

Getting started

You can learn about application of the RDS instance via Getting Started. For details, see Getting Started.