ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #yugabytedb
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.
An architecture note on the smallest YugabyteDB cluster worth running: three nodes, three zones, RF 3, with tablets as Raft groups. Covers placement flags, operational checks, and the failure modes that should trigger a redesign.
Geo‑partitioning in YugabyteDB lets you enforce data residency with a placement policy. This note covers requirements, minimal design, trust boundaries, operational checks, failure modes, and when the design must change.
Learn how YugabyteDB follower reads let you serve SELECT queries from replica tablets to cut read latency, with a concrete example, setup steps, and consistency trade‑offs.
Stop wasting milliseconds on network shuffles. Learn how YugabyteDB Colocated Tables keep related data on the same node to accelerate joins in multi‑tenant apps.
Detect and correct tablet distribution skew in YugabyteDB by checking tablet counts per node, enabling the load balancer, and triggering a rebalance.
Learn how to balance performance and consistency in YugabyteDB by choosing between Strong Global Consistency and Snapshot Isolation for distributed workloads.