Cockroach Lab’s decision to move away from open source has reignited the debate on the long-term viability of open source projects, and how companies can find success with this business model. Discover why Yugabyte co-founder Karthik Ranganathan believes that open source (and PostgreSQL) is the future, and the reasons why YugabyteDB is (and will continue to be) fully open.
At the Distributed SQL Summit 2020, James Hartig – Co-Founder at Admiral, presented the talk “How Admiral Scales Globally with YugabyteDB on Google Cloud While Maintaining Single-Digit Latency.”
Admiral’s Go application runs in Google Cloud across 5 regions in 3 continents. This geo-distributed architecture is powered by a single YugabyteDB cluster that delivers an average global read latency of 3ms! In this talk,
…
Earlier this week, Yugabyte CTO Karthik Ranganathan presented the live webinar: Evaluating CockroachDB vs YugabyteDB, with a spotlight on comparing PostgreSQL features, architecture, and the latest performance benchmarks between the two databases. We were delighted to see such interest in the topic, dive deeper into some of the topics we raised in parts 1 and parts 2 of the blog series, Bringing Truth to Competitive Benchmark Claims – YugabyteDB vs CockroachDB, and answer questions from the audience.
…
In part 1 of this blog series, we highlighted multiple factual errors in the Cockroach Labs analysis of YugabyteDB. In this second YugabyteDB vs CockroachDB post we provide the next layer of detail behind YugabyteDB’s architecture, with an emphasis on comparing it to that of CockroachDB’s.
Yugabyte SQL is based on a reuse of PostgreSQL’s native query layer.
…
At Yugabyte, we welcome competition and criticism. We believe these aspects are essential to the wide adoption of a business-critical, fully open source project like YugabyteDB. Specifically, constructive criticism helps us improve the project for the benefit of our large community of users. Engineers at Cockroach Labs posted their analysis of how CockroachDB compares with YugabyteDB a few months ago. We thank them for taking the time to do so.
…
This post addresses a concern raised about a benchmarking result we recently published comparing the performance of YugabyteDB, Amazon Aurora and CockroachDB. It was pointed out that we unfairly used the default isolation level for each database rather than use serializable isolation level in all databases (even though serializable level was not required for these workloads). In addition, we are also happy to share additional results with the workloads run at YugabyteDB’s serializable isolation level.
…
One of the flagship features of the Yugabyte distributed SQL database is the PostgreSQL-compatible YSQL API. Let’s take a look at the performance and scalability of YSQL and compare it to two other PostgreSQL-compatible databases—Amazon Aurora PostgreSQL and CockroachDB.
This benchmarking blog comparing YugabyteDB vs CockroachDB highlights key differences in handling distributed SQL workloads, emphasizing performance and feature advantages.
