Community

Community Blog Cloud Forward Episode 6: Cloud-Native Database - PolarDB | Strict Consistency Cluster

Cloud Forward Episode 6: Cloud-Native Database - PolarDB | Strict Consistency Cluster

Strict Consistency Cluster was introduced to PolarDB to solve inconsistency issues caused by delayed reading from RO nodes.

How can we address the issue of read delays when using a one-primary-multi-standby database architecture?

How do we maintain strong consistency?

Hello and welcome to another episode of Cloud Forward.

Today, we'll show you how we can increase the overall throughput capacity of a cluster to solve the problem of delayed reads from standby nodes.

The read-only node provides eventual read consistency by default in a one-primary-multi-standby database architecture.

Although physical replication and shared storage technologies can significantly reduce the latency of read-only nodes, they cannot guarantee that read requests sent to the read-only nodes get the latest data written on the primary node.

As a result, delayed reading from the read-only nodes can cause inconsistency issues, especially for businesses in industries sensitive to data latency.

Let's take a look at how PolarDB addresses the issue.

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

Database performance POLARDB cloud native relational database management system Cloud Forward Strict Consistency Cluster

0 0 0

Share on

Read previous post:

Cloud Forward Episode 5: Cloud-Native Database - PolarDB | Multi-Primary

Community

Cloud Forward Episode 6: Cloud-Native Database - PolarDB | Strict Consistency Cluster

Read previous post:

Read next post:

ApsaraDB

You may also like

Comments

ApsaraDB

Related Products

PolarDB for MySQL

PolarDB for PostgreSQL

PolarDB for Xscale

Database for FinTech Solution