11–20 of 49 posts
Yugabyte has great articles in general and seems almost to be good to be true what I have read. It is just missing a bit of independent third party reviews but it does look interesting. Anyone with hands on experience?
Yugabyte v. Cockroach analysis: https://www.cockroachlabs.com/blog/unpacking-competitive-ben... disclaimer: I work at cockroach
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.
Does anyone have good experiences with seamless sharding at the database layer? I'm old school and I'd be strongly inclined to look for a simple cut that allowed me to shard at the app layer, but I'd love to hear an alternative view.
Yugabyte has great articles in general and seems almost to be good to be true what I have read. It is just missing a bit of independent third party reviews but it does look interesting. Anyone with hands on experience?
https://jepsen.io/analyses/yugabyte-db-1.3.1
> 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 tried Yugabyte a few weeks back, the TServer kept crashing while my backend was creating some very simple tables. I'm stuck with CockroachDB for the time being.
> I'm stuck with CockroachDB for the time being. Would you care to share any negative experiences you've had with CockroachDB? What is motivating your desire to look elsewhere?
CockroachDB Core is fine as a product, the docs are up to date and it's not hard to operate, all that is appreciated it. I just don't think I'm the target user, unless you make a shit ton of money as you scale it will be hard to operate without:
- Distributed Backups(Enterprise)
- Follower Reads(Enterprise) (no, follow-the-workload doesn't cut it)
- RBAC(Enterprise)
Yugabyte offers all that in their open-source license, which is why I'm rooting for them, that in addition to Change Data capture(Enterprise offering in CockroachDB) is also included.
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
https://jepsen.io/analyses/yugabyte-db-1.3.1
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 in…
I tried Yugabyte a few weeks back, the TServer kept crashing while my backend was creating some very simple tables. I'm stuck with CockroachDB for the time being.
Have you tried comdb2? I've heard good things. Idk why it isn't more popular.