ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
YugabyteDB’s follower‑read feature routes read‑only queries to replicas, offloading the leader and cutting latency in geo‑distributed clusters. Enable with a session variable, verify via tablet‑server logs, and watch leader CPU drop. Trade‑off: staleness; not for write‑heavy paths.
A decision guide for picking YSQL or YCQL in YugabyteDB, covering consistency models, performance trade-offs, and a concrete validation workflow for test clusters.
Geo-partitioning in YugabyteDB pins table partitions to regional tablespaces so writes reach consensus locally instead of across oceans — here's the DDL, the verification steps, and the availability trade-off.
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.
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.
yugabytedb