Cloud Forward Episode 7: Cloud-Native Database - PolarDB | Transparent Read/Write Splitting

The need for more reads and fewer writes places enormous pressure on the database's read capacity. To solve this issue, here comes the R/W splitting.

How can read and write operations be separated in a simple and efficient manner?

Hello and welcome to another episode of Cloud Forward.

Today, we’ll discuss read and write splitting.

In industries such as e-commerce, the need for more reads and fewer writes places enormous pressure on the database's read capacity, which may eventually affect the business.

We would naturally think of read and write splitting to solve this issue.

Conceptually, it is straightforward, but the real question is how?

What if we use a single cluster address as a proxy to re-route read and write requests?

The concept evolved into the PolarProxy; it's transparent, highly available, and has an adaptive load balancing capability.

Through PolarProxy, SQL requests are automatically forwarded to each node of the PolarDB cluster, providing high-performance, high-throughput, concurrent SQL processing capabilities.

So, applications only need to connect to one single cluster address, and write requests are automatically routed to the primary node, while read requests are routed to the primary or read-only nodes, based on the loads on each node.

Watch the full video here to learn more about PolarDB >>

0 0 0

Share on

: ApsaraDB

495 posts | 147 followers
Follow

Community

Cloud Forward Episode 7: Cloud-Native Database - PolarDB | Transparent Read/Write Splitting

Read previous post:

Read next post:

ApsaraDB

You may also like

Comments

ApsaraDB

Related Products

PolarDB for PostgreSQL

PolarDB for Xscale

PolarDB for MySQL

Database for FinTech Solution