During a massive Texas snowstorm, a power failure affected millions of homes, businesses, and even one of our largest retail customer’s data centers. Despite the widespread chaos, they managed to maintain application availability thanks to YugabyteDB’s geo-distributed cluster, a solution we’ll explore in this blog post.
Distributed SQL offers greater scalability, availability, and geo-distribution of data compared to PostgreSQL, but it is important to understand the differences in behaviors between the two systems in order to make the most of your distributed SQL database.
YugabyteDB uses LSM Tree / SST Files to minimize the risk of data corruption, in contrast to PostgreSQL’s method. This approach, coupled with independent compactions and checksum verification, enhances data integrity.
This edition of the Distributed SQL Tips and Tricks blog looks at a simple and efficient approach to achieve TTL-like functionality in YSQL API using database partitions.
This edition of the Distributed SQL Tips and Tricks blog looks at how to use READ COMMITTED isolation in YugabyteDB to avoid restart errors in YSQL, ensuring a smoother database experience.
This edition of the Distributed SQL Tips and Tricks blog looks how and why Yugabyte handles efficient row retrieval using a primary key, as well as the implications of not having one.
YugabyteDB supports two methods of sharding data: by hash and by range. Discover which strategy is correct to use in which situation.
When considering replication options between YugabyteDB clusters, you have two options—xCluster async replication or setting up Kafka. Learn the when and how and why to both choices.
This edition of the Distributed SQL Tips and Tricks blog looks at YugabyteDB’s support for composite keys for tables (as well as secondary indexes).
This edition of the Distributed SQL Tips and Tricks blog looks at how to achieve region-level fault tolerance with row-level geo-partitioning.
