PostgreSQL offers robust features but has certain limitations in scalability, replication, resilience (and more). YugabyteDB addresses these issues through distributed design, storage efficiency, and transaction handling, providing a comprehensive solution when high availability, ACID, and scale are mandatory.
Explore the different data replication options available with YugabyteDB including synchronous, asynchronous, read replicas, xCluster, and change data capture (CDC).
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.
Despite advancements in public clouds, region and zone outages still occur once or twice a year. This blog offers best practices to improve performance and reduce latencies in a multi-region deployment.
Discover how to best achieve high availability and disaster recovery using two data centers. This blog compares traditional monolithic databases with distributed SQL, and then discusses how it is all possible using YugabyteDB with cross-cluster replication capabilities.
In this blog post, we will discuss how to maintain transactional read guarantees on an async standby configured through cross cluster replication. This feature has bearing on any user who runs a transactional application in a distributed setup. We think that may apply to many people reading this blog.
We have performed our own Jepsen testing on YugabyteDB, and the open-source repository reveals no correctness failures; we’re also working on adding more tests to ensure our database holds true to its promises.
MongoDB’s sharding and replication have improved since it was first an AP database, but it still has limitations for highly scalable and latency-sensitive apps. In this blog, the authors discuss why users switch to YugabyteDB due to distributed ACID transactions and improved scalability.