Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CockroachDB 19.2

cockroachlabs.com

Post reply on HN
Print view View original

41–50 of 63 posts

Re: CockroachDB 19.2

#41

Post by manigandham »

cglace wrote: post #16

How does CockroachDB compare to YugabyteDB

CockroachDB is built from scratch in Go, uses Raft + RocksDB as a distributed key/value store, and then implements the Postgres data structures and wire protocol on top. Focuses on strong consistency and durability (which was the origin of its name). Can run active/active in multiple regions. Lacks full compatibility with Postgres.

Yugabyte is a multi-model database built in C++, uses Raft + RocksDB as a distributed key/value store, and then implements a proprietary document-store model on top called DocsDB. This is exposed as a Redis API, Cassandra API, and now PostgreSQL RDBMS interface by using the actual Postgres code for the SQL layer. Much higher compatibility with Postgres with all data types, most advanced SQL, and even some extensions that work without problems. Not as advanced on the distributed side and uses more of a primary/replica setup.

Both are great options for a distributed scalable RDBMS with Postgres.

Re: CockroachDB 19.2

#42

Post by outside1234 »

gigatexal wrote: post #37
outside1234 wrote: post #26

Earlier quoted context omitted.

Yeah, that is not a real solution for a database of any real size, which is the only reason to use CockroachDB in the first place.

I know. It’s a bummer. I’ve not tried to do block level backups for our setup in production.

I have - it doesn't work sadly. :(

Re: CockroachDB 19.2

#43

Post by bithavoc »

sandstrom wrote: post #34

Awesome to see a new release! We've followed Cockroach for a while, would be a good fit four our workload. However, I think it's sad that their pricing is so opaque. Even after a few emails back and forth with their sales people it still feels fairly arbitrary, and since it's not transparent we don't know if they're just making numbers up based on what they think we're willing to pay. I find this sales-tactic off-put…

This is so true, I had the exact same experience last year (back then they says it was something like 700 USD per core yearly for the startup plan), decided to table the offer and use their dump backups until I was bigger. Then they released Regional replicas as an enterprise feature and realized their core offering was complete and all the new cool stuff was going for their paid enterprise offering. Then they became proprietary and lost me completely. If I ever need distributed read replicas I can do it myself with Postgres or just use AWS RDS. My money is on Yugabyte now.

Re: CockroachDB 19.2

#44

Post by rubyn00bie »

Is the primary advantage of CockroachDB over FoundationDB primarily in supporting SQL out of the box? The multi-region support seems pretty banger at first glance.

P.S.

... and I had a tirade here about the licensing information being largely absent on their FAQ or product pages, but I did find this after a google before posting:

https://www.cockroachlabs.com/blog/oss-relicensing-cockroach...

which... from what I can tell at my cursory inspection, seems okay to me. I'd be pretty pissed too assuming a giant SaaS company came by, forked their product, and then resold it with improvements they didn't upstream. Mostly, because it's just fucking rude. One could have a good business relationship with another company with both prospering, but instead you take the short-n-shitty road for no reason...

With that said, it'd be nice if you put that in yer FAQ.

Re: CockroachDB 19.2

#45

Post by zzyzxd »

jseldess wrote: post #21
ralusek wrote: post #15

Some comments I have regarding the documentation. It seems like there is a lot describing how to set up a cluster and how to do various SQL operations that most people probably know how to do. I think the information that should be presented much more clearly are: 1.) How do we have to partition our data/what restrictions are in place? Basically, what considerations are necessary when designing the data model due to…

Head of Docs and Training at Cockroach Labs here. Thanks for this feedback, ralusek. It's spot on, and we're planning to create much more direct and prescriptive guidance and best practices for working with CockroachDB across multiple regions. That's when placement of data (via geo-partitioning or other approaches) is crucial for reducing network latency. In case you haven't seen them, for now, we have docs on some d…

Last month I tried to deploy cockroachdb in Kubernetes and I felt the documentation wanted to treat me like a 5-year-old.

I don't think the your product documentation has to explain what Kubernetes is or its terminologies[1].

The worst part is that it does not tell the cluster admins what need to be setup in the Kubernetes cluster at all, instead, it wraps a bunch of `kubectl` commands in a Python script and says "just download the script and run it"[2]. I know a simple `python setup.py` command is easier for novice to just try out. But it could really gives seasoned Kubernetes admins some headache...Our clusters enforce GitOps and nothing can bypass pull requests. Running some random `kubectl` commands is simply impossible. I ended up spending my day reading and translating the script into Kubernetes object definitions by hand and I didn't enjoy it...

1. https://www.cockroachlabs.com/docs/stable/orchestrate-cockro... 2. https://github.com/cockroachdb/cockroach/blob/master/cloud/k...

Re: CockroachDB 19.2

#47

Post by awoods187 »

aaronbwebber wrote: post #35
irfansharif wrote: post #12

Earlier quoted context omitted.

You can find our more recent performance numbers on https://www.cockroachlabs.com/docs/v19.2/performance.html

Is that saying that you are comparing Cockroach running on 81 c5d.9xls vs Aurora running on 2 r3.8xls? I get that part of what you are trying to show is that Cockroach will scale far past what any single-master system can, but it feels pretty lame to run a test comparing transaction throughput on 2900 cores vs 64 cores and a data set size comparison on 81 hosts vs 2. The sysbench metrics seems like a much fairer comp…

Hi- product manager from CRL here. You are right--we hope to demonstrate that CockroachDB is built to scale horizontally. Deployments of CockroachDB can grow by easily adding more nodes to the cluster which in turn linearly scales throughput. We have posted the most recent published Aurora numbers as a comparison to demonstrate how architecture can influence scale.

We also hear your point about efficiency as tpmC (throughput) alone isn't sufficient to compare systems without taking hardware into account. TPC-C asks users to provide a tpmC per dollar amount. We conducted this price comparison previously in this blog post https://www.cockroachlabs.com/blog/cockroachdb-2dot1-perform.... These results are even lower in 19.2 because we can achieve greater tpmC with fewer nodes.

This page wasn't met to be competitive-we simply showed Aurora as a reference point. Since we want to focus on CockroachDB we will remove the Aurora comparison.

Re: CockroachDB 19.2

#48

Post by bogomipz »

manigandham wrote: post #41
cglace wrote: post #16

How does CockroachDB compare to YugabyteDB

CockroachDB is built from scratch in Go, uses Raft + RocksDB as a distributed key/value store, and then implements the Postgres data structures and wire protocol on top. Focuses on strong consistency and durability (which was the origin of its name). Can run active/active in multiple regions. Lacks full compatibility with Postgres. Yugabyte is a multi-model database built in C++, uses Raft + RocksDB as a distributed…

Thanks for this overview. Is Cockroach an open-source version of Google's Spanner as well?

Re: CockroachDB 19.2

#49

Post by jaytaylor »

rubyn00bie wrote: post #44

Is the primary advantage of CockroachDB over FoundationDB primarily in supporting SQL out of the box? The multi-region support seems pretty banger at first glance. P.S. ... and I had a tirade here about the licensing information being largely absent on their FAQ or product pages, but I did find this after a google before posting: https://www.cockroachlabs.com/blog/oss-relicensing-cockroach... which... from what I can…

> Is the primary advantage of CockroachDB over FoundationDB primarily in supporting SQL out of the box.

That + foundation db pulled the carpet out from all their users at the time apple purchased them. Cannot trust that team / product again, it would be incredibly and blasphemously foolish. At least CDB likely won't pull any such stunt.

Disclaimer: I was personally affected by the FDB team making this choice back in 2015 when events unfolded. Still leaves a bitter taste.

Re: CockroachDB 19.2

#50

Post by irfansharif »

bogomipz wrote: post #48
manigandham wrote: post #41

Earlier quoted context omitted.

CockroachDB is built from scratch in Go, uses Raft + RocksDB as a distributed key/value store, and then implements the Postgres data structures and wire protocol on top. Focuses on strong consistency and durability (which was the origin of its name). Can run active/active in multiple regions. Lacks full compatibility with Postgres. Yugabyte is a multi-model database built in C++, uses Raft + RocksDB as a distributed…

Thanks for this overview. Is Cockroach an open-source version of Google's Spanner as well?

Not technically open-source (BSL-licensed), but yes, source available on https://github.com/cockroachdb/cockroach/.
Post reply on HN