CockroachDB 1.0 • Hacker News Board

Re: CockroachDB 1.0

#31

Post by irfansharif » Wed, May 10, 2017, 2:41 PM UTC

dmix wrote: post #25

dis-sys wrote: post #6

I really like the fact that the CockroachDB team recently did a detailed Jepsen test with Aphyr. The follow up articles from both CockroachDB and Aphyr explaining the findings are very interesting to read. For those who might be interested - https://www.cockroachlabs.com/blog/cockroachdb-beta-passes-j... https://jepsen.io/analyses/cockroachdb-beta-20160829

> CockroachDB is a distributed, scale-out SQL database which relies on hybrid logical clocks I was curious what "hybrid logical clocks" meant and found the linked paper a bit over my head. I found this more layman description: http://muratbuffalo.blogspot.ca/2014/07/hybrid-logical-clock... Apparently Google used GPS/atomic clocks to keep time synced: >> To alleviate the problems of large ε, Google's TrueTime (TT) emp…

You might find our post[1] on atomic clocks, rather having to do without them, partially interesting.

[1]: https://www.cockroachlabs.com/blog/living-without-atomic-clo...

Re: CockroachDB 1.0

#32

Post by brightball » Wed, May 10, 2017, 2:41 PM UTC

How does it compare to Couchbase with it N1QL?

Re: CockroachDB 1.0

#33

Post by dianasaur323 » Wed, May 10, 2017, 2:42 PM UTC

sergiotapia wrote: post #22

Is Cockroach DB intended for just "big-data" companies? Would a small project run really well with Cockroach DB? Of course a small database probably won't need a lot of the unique features, but is this aiming to replace PG/MySQL in the small/mid-size projects?

[cockroachdb here] Yes! In addition to being highly scalable, CockroachDB also comes with built-in replication. That means that even with a smaller project that hasn't scaled yet, you still get the benefit of a more resilient database.

Also, CockroachDB is super easy to install and get started with!

Re: CockroachDB 1.0

#34

Post by Perignon » Wed, May 10, 2017, 2:45 PM UTC

Name still sucks and is disgusting af.

Re: CockroachDB 1.0

#35

Post by dianasaur323 » Wed, May 10, 2017, 2:45 PM UTC

bpicolo wrote: post #20

misterbowfinger wrote: post #11

Can someone give a brief pros/cons between Cockroach DB Core and Google Cloud Spanner?

Open source vs not open source. Cockroach still in it's infancy vs spanner. I'm sure there are a variety of things here, but they mostly aim to solve a similar problem with a slightly different approach. Some of the big details relate to not requiring atomic clocks: https://www.cockroachlabs.com/blog/living-without-atomic-clo... Here's their comparison chart, though naturally it's biased for things-cockroach-does: ht…

[cockroachdb here] Thanks for the great response, bpicolo!

Re: CockroachDB 1.0

#36

Post by socmag » Wed, May 10, 2017, 2:46 PM UTC

Clocks are meaningless under load.

The higher frequency the transactions the more you get into quantum physics.

In reality, nobody cares if T-Mobile debited your account 0.01ms before WalMart.

[edit] what is important is isolation and consistency of the transactons.

Re: CockroachDB 1.0

#37

Post by scandox » Wed, May 10, 2017, 2:47 PM UTC

johnwheeler wrote: post #28

I think the name "Cockroach" was a really poor decision from a marketing standpoint. The team intended to convey durability, since cockroaches can live through anything. But when I think of a cockroach, I think, gross, disgusting, etc.

It's memorable. So if the product is really excellent and is needed by customers - then I think it could be a boon.

I mean Mongo has very bad associations for me in terms of childhood taunts and Blazing Saddles...but now the name really relates more to the product than to the original meaning.

Re: CockroachDB 1.0

#38

Post by irfansharif » Wed, May 10, 2017, 2:49 PM UTC

ericb wrote: post #30

Can Cockroach be plugged into a Rails app where mysql was? I'd be interested in hearing: - the backup story - the replication/failover story - horizontal scaling story (is it plug and play)

Not mysql, but we've tested and recommend the Ruby pg driver and the ActiveRecord ORM[1] (CockroachDB supports the PostgreSQL wire protocol). It should be 'plug and play' insofar as you simply point to any node in the running cluster when setting up ActiveRecord::Base.establish_connection.

As for our backup story, our doc page[2] on the subject should shed more details.

[1]: https://www.cockroachlabs.com/docs/build-a-ruby-app-with-coc...

[2]: https://www.cockroachlabs.com/docs/backup.html

Re: CockroachDB 1.0

#39

Post by rodionos » Wed, May 10, 2017, 2:51 PM UTC

dis-sys wrote: post #6

I really like the fact that the CockroachDB team recently did a detailed Jepsen test with Aphyr. The follow up articles from both CockroachDB and Aphyr explaining the findings are very interesting to read. For those who might be interested - https://www.cockroachlabs.com/blog/cockroachdb-beta-passes-j... https://jepsen.io/analyses/cockroachdb-beta-20160829

> When a node exceeds the clock offset threshold, it will automatically shut down to prevent anomalies.

If you're planning to run on VMware, be prepared to handle rather dramatic system clock shifts. I've seen shifts of up to 5 minutes during heavy backup windows. Not all customers might be willing to have their nodes go down due to system clock / NTP issues.

Re: CockroachDB 1.0

#40

Post by gm » Wed, May 10, 2017, 2:51 PM UTC

johnwheeler wrote: post #28

I think the name "Cockroach" was a really poor decision from a marketing standpoint. The team intended to convey durability, since cockroaches can live through anything. But when I think of a cockroach, I think, gross, disgusting, etc.

Agreed. It's a very stupid name. It's memorable for all the wrong reasons: It detracts from the product, and takes attention away from the product to the product name that elicits a visceral disgust in a lot of people. The conversation then is about why the product is called that instead of the product's merits.