ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #yugabytedb
Use YugabyteDB follower reads for staleness-tolerant SELECTs to reduce leader load, but avoid them for reads that must reflect immediately committed writes.
Learn how to use YugabyteDB follower reads to reduce geo-distributed read latency from 100ms+ to single-digit milliseconds by serving requests from local replicas.
YugabyteDB’s UPSERT works like PostgreSQL’s INSERT … ON CONFLICT, but it’s implemented as a single Paxos proposal per key. This gives ACID guarantees across shards, yet high contention can spike latency. Learn how to use it safely, verify it, and know the trade‑offs.
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.
Learn how to use YSQL range partitioning in YugabyteDB 8.0+ to eliminate write hotspots and distribute time-series data across cluster nodes while maintaining ACID compliance.
A step-by-step diagnostic guide for intermittent query failures caused by leader loss in YugabyteDB clusters. Covers recognizable symptoms, a cause/diagnostic table, ordered checks with commands, targeted fixes, and escalation criteria for production environments.
A decision guide for picking YSQL or YCQL in YugabyteDB, covering consistency models, performance trade-offs, and a concrete validation workflow for test clusters.
Learn how to configure YugabyteDB read replicas with timeline consistency to serve low‑latency, bounded‑staleness reads from geo‑distributed regions.
Route catalog reads to local YugabyteDB followers with bounded staleness while keeping inventory writes on the leader.