Live data from Hacker News

Distributed SQL vs. NewSQL

blog.yugabyte.com

1–10 of 49 posts

Re: Distributed SQL vs. NewSQL

#2
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.

Re: Distributed SQL vs. NewSQL

#4
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?

Re: Distributed SQL vs. NewSQL

#7
post #6

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.

Re: Distributed SQL vs. NewSQL

#8
post #5
post #4

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

[deleted]

Re: Distributed SQL vs. NewSQL

#9
post #6

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?

Re: Distributed SQL vs. NewSQL

#10
post #4

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

Post reply on HN