You can join the discussion about the results on HackerNews here.
Last year we published our DIY Jepsen testing results – including the tests and failure modes implemented as well as the bugs found. We recently engaged Kyle Kingsbury, the creator of the Jepsen test suite, for an official analysis and are happy to report that YugabyteDB 1.2 formally passes Jepsen tests using the YCQL API.
…
Our previous post dived into the details of the storage layer of YugabyteDB called DocDB, a distributed document store inspired by Google Spanner. This post focuses on Yugabyte SQL (YSQL), a distributed, highly resilient, PostgreSQL-compatible SQL API layer powered by DocDB. A follow-up post will highlight the challenges faced and lessons learned when engineering such a database.
Yugabyte SQL (YSQL) is a distributed and highly resilient SQL layer,
…
In this post, we dive into the architecture of the distributed storage layer of YugabyteDB, which is inspired by Google Spanner’s design
The team at YugaByte is excited to announce that YugabyteDB 1.2 is officially GA! You can download the latest version from our Quick Start page.
YugaByte SQL (YSQL) is our PostgreSQL v11 compatible, distributed SQL API. It is ideal for powering microservices that require low latency, internet scale, geographic data distribution and extreme resilience to failures but want the data modeling flexibility of SQL (joins,
…
In this post, we comparethe high availability and transactions architecture of PostgreSQL and MongoDB to that of YugabyteDB.
In this post, we reviewed the building blocks of the YugabyteDB and mapped them to the corresponding concepts (if any) in PostgreSQL and MongoDB.
As described in our previous post “How We Built a High Performance Document Store on RocksDB?”, YugabyteDB’s distributed document store (DocDB) uses RocksDB as its per-node storage engine. We made multiple performance and data density related enhancements to RocksDB in the course of embedding it into DocDB’s document storage layer (figure below). These enhancements are distributed as part of the YugabyteDB open source project. The goal of this post is to deep dive into these enhancements for the benefit of engineering teams interested in leveraging RocksDB beyond its original design intent of a fast monolithic key-value store.
…
FoundationDB enjoys a unique spot in the transactional NoSQL space given its positioning as a basic key-value database that can be used to build new, more application-friendly databases. Given that many of the guarantees provided by its core engine (such as multi-shard ACID transactions and high fault tolerance) are similar to those provided by the YugabyteDB database, our users often ask us for a comparison. These users are essentially trying to understand whether they should build their app directly using one of the three YugabyteDB APIs or should they explore/build a new database layer on FoundationDB first.
…
Our post Getting Started with Distributed Backups in YugabyteDB details the core architecture powering distributed backups in YugabyteDB. It also highlights a few backup/restore operations in a single region, multi-AZ cluster. In this post, we perform distributed backups in a multi-region YugabyteDB cluster and verify that we achieve performance characteristics similar to those observed in a single region cluster.
We configured a 9 node cluster with 3 availability zones across 2 regions and repeated the benchmark introduced in the post.
…
YugabyteDB is a distributed database with a Google Spanner-inspired strongly consistent replication architecture that is purpose-built for high availability and high performance. This architecture allows administrators to place replicas in independent fault domains, which can be either availability zones or racks in a single region or different regions altogether. These types of multi-AZ or multi-region deployments have the immediate advantage of guaranteeing organizations a higher order of resilience in the event of a zone or region failure.
…
