Offload YugabyteDB Read Traffic with Follower Reads
YugabyteDB follower reads serve SELECT queries from replicas instead of the Raft leader, reducing leader load at the cost of possible read staleness.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
YugabyteDB follower reads serve SELECT queries from replicas instead of the Raft leader, reducing leader load at the cost of possible read staleness.
Route catalog reads to local YugabyteDB followers with bounded staleness while keeping inventory writes on the leader.
Learn how YugabyteDB’s follower reads let any replica serve reads, cutting multi-region latency while accepting bounded staleness.
YugabyteDB follower reads let nearby replicas serve SELECTs with a bounded staleness guarantee, cutting cross-region read latency. Here's how to configure, verify, and size the trade-off.
Follower reads route SELECT queries to nearby replicas, cutting cross-region read latency at the cost of a configurable staleness bound (default 30 s). Enable it with yb_read_from_followers, verify with a benchmark, and keep leader reads for read-after-write consistency.
Follower reads let a YugabyteDB session read from a local Raft follower instead of a cross-region leader. Here's the trade, a worked YSQL example, and how to verify it.
Follower reads let YugabyteDB geo-distributed apps serve reads from local tablet replicas with a bounded staleness, cutting cross-region latency without schema changes.