CockroachDB 1.0 • Hacker News Board

Re: CockroachDB 1.0

#21

Post by chuckledog » Wed, May 10, 2017, 2:33 PM UTC

nik736 wrote: post #10

What advantages do I have using Cockroach compared to Postgres, Cassandra, Rethink or MongoDB? (I know that all of them are completely different, that's part of the question)

From the linked website: "CockroachDB provides scale without sacrificing SQL functionality. It offers fully-distributed ACID transactions, zero-downtime schema changes, and support for secondary indexes and foreign keys". Significantly, CockroachDB has had extensive design dedicated to surviving adverse network conditions (see Jepsen references in other posts)

Re: CockroachDB 1.0

#22

Post by sergiotapia » Wed, May 10, 2017, 2:34 PM UTC

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?

Re: CockroachDB 1.0

#23

Post by niceperson » Wed, May 10, 2017, 2:35 PM UTC

>Cockroach

What were they thinking?

Re: CockroachDB 1.0

#24

Post by s_kilk » Wed, May 10, 2017, 2:35 PM UTC

cwisecarver wrote: post #3

Cue the comments stating that no one will use this because the name is bad.

Maybe they want to keep all the startup webscale dweebs out.

Re: CockroachDB 1.0

#25

Post by dmix » Wed, May 10, 2017, 2:37 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

> 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) employs GPS/atomic clocks to achieve tight-synchronization (ε=6ms), however the cost of adding the required support infrastructure can be prohibitive and ε=6ms is still a non-negligible time.

And CockroachDB created more of a hybrid version that works on commodity hardware.

Distributed systems programming sounds endlessly challenging as you are always balancing trade-offs.

Re: CockroachDB 1.0

#26

Post by cholantesh » Wed, May 10, 2017, 2:38 PM UTC

mirekrusin wrote: post #19

cwisecarver wrote: post #3

Cue the comments stating that no one will use this because the name is bad.

Just call it C9DB if you don't want to use the c-word.

Wouldn't it be C8DB?

Re: CockroachDB 1.0

#27

Post by [deleted] » Wed, May 10, 2017, 2:39 PM UTC

[deleted]

Re: CockroachDB 1.0

#28

Post by johnwheeler » Wed, May 10, 2017, 2:39 PM UTC

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.

Re: CockroachDB 1.0

#29

Post by zzzcpan » Wed, May 10, 2017, 2:40 PM UTC

nik736 wrote: post #10

What advantages do I have using Cockroach compared to Postgres, Cassandra, Rethink or MongoDB? (I know that all of them are completely different, that's part of the question)

They are targeting MySQL/Postgres users, basically a post-CAP approach to RDBMS. But if you can work with eventual consistency, they are definitely not your first choice.

Re: CockroachDB 1.0

#30

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

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)