Yugabyte v. Cockroach analysis: https://www.cockroachlabs.com/blog/unpacking-competitive-ben...

disclaimer: I work at cockroach

Nice. Seems a bit disingenuous on yugabyte to claim they’re better performant in light of this.

Just want to say that I love your docs. Haven’t used cockroachDB just yet but the docs are clean, easy to follow, devoid of marketing and focused on facts.

Second that, the CockroachDB documentation is excellent. All the DDL and DML statements are clearly documented and with examples, that's really cool.

Thanks, that is exactly the kind of third party analysis I was looking for to add some color to all of Yugabyte's claims

Oh good. I had not seen this blog post from CRDB, and I had asked this exact question 4 months ago: https://news.ycombinator.com/item?id=21007562

From your link:

> 2019-09-05: YugaByte’s blog post states YugaByte DB “passes Jepsen tests”. We feel obligated to state that YugaByte DB’s Jepsen test suite does not pass, though it may in the future. Race conditions in YugaByte DB’s schema system can cause correctness errors. For example, inserting rows into a freshly-created table with DEFAULT values may result in the values for those columns initialized to NULL instead. We can also now confirm that this issue affects all default values, not just DEFAULT NOW(). It also appears that DDL race conditions might, under certain conditions, render tables completely unusable.

Yikes. I understand the need for marketing and making their product look good but it's going a bit too far saying they pass the tests when they didn't. I can easily see potential customers pausing when encountering that kind of attitude from YugabyteDB's developers. "What else are they dishonest about..." kind of idea.

I don’t know the case at yugabyte but, in general, the outright lies by sales has nothing to do with the integrity of the developers.

Developers are responsible for fair benchmarks.