PolarDB:PolarProxy

PolarDB architecture and PolarProxy

PolarDB Cluster Edition has the following characteristics:

• A PolarDB cluster consists of one primary node and one or more read-only nodes.

• By default, PolarDB provides two types of endpoints: primary endpoints and cluster endpoints.

  Note

  The requests from the applications that are connected to cluster endpoints must pass through PolarProxy. Cluster endpoints are classified into read-only cluster endpoints and read/write cluster endpoints. Read-only cluster endpoints allow PolarDB clusters to distribute read requests to read-only nodes based on the number of connections. For information about read/write cluster endpoints, see Read/write splitting.

Read/write splitting

Read/writing splitting is automatically performed in the PolarDB clusters of the Cluster Edition. After an application is connected to a cluster endpoint of a PolarDB cluster, the write requests from the application are forwarded to the primary node of the cluster and read requests are forwarded to the primary and read-only nodes based on the load of each node. The number of pending requests on a node indicates the load of the node. For more information, see Read/write splitting.

Transaction splitting

PolarDB supports transaction splitting. Transaction splitting ensures that data is consistent in a session and allows PolarDB to send read requests to read-only nodes to reduce the load of the primary node. For more information, see Transaction splitting.

Related API operations