How is intra node latency handled during updates?

All we need is an easy explanation of the problem, so here it is.

Yugabytedb is a distributed rdbms. It uses data redundancy. How does it keep a good performance while having to keep multiple copies up to date?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

Reads go to the raft leader and writes as well but wait for the quorum. So it depends on the topology. A Replication Factor RF=3 on one AWS region, for example, doesn’t suffer as latency between AZs is low. For cross-region distribution, this is addressed with placement preferences. Like having all leaders near the users, and one nearby region will answer the quorum.
Those preferences can be mapped to business info (like customer’s country) through PostgreSQL partitioning and tablespaces

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply