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

What to Expect in CockroachDB 1.0

cockroachlabs.com

Post reply on HN
Print view View original

31–40 of 47 posts

Re: What to Expect in CockroachDB 1.0

#31

Post by BramG »

si13 wrote: post #29

Is .net core a second class citizen? Why dont you care c# clients (npgsql)

.Net wasn't a priority due to our very limited resources. We will be expanding the number of drivers and ORMs greatly over the next while.

That being said, I tested npgsql a few days ago and it worked perfectly. Nothing too extensive, just created a db, 2 tables, inserted some data and did a join. So please give it a shot and if it doesn't work, file issues and we'll address them.

(disclosure: I work at cockroach labs)

Re: What to Expect in CockroachDB 1.0

#32

Post by elvinyung »

didip wrote: post #5

Any newer Jepsen test since this one: https://jepsen.io/analyses/cockroachdb-beta-20160829 Also, how's the performance nowadays?

I noticed that the question on performance was ignored, but I think it's worth noting that FoundationDB died on exactly the same beach. [1] I'm not extremely familiar with the CockroachDB architecture (other than "it's kinda like the F1/Spanner/Bigtable stack"), but I suspect that there are some commonalities. For example, CockroachDB's Bigtable-style two-level range indexing means you could run into exactly this problem:

> FDB-SQL stores metadata in the KV store itself. This is great from a distributed correctness point-of-view. It’s also great from a simplicity point-of-view. If I trust the underlying system to be safe and consistent, then my metadata is also safe and consistent. But now I need to do a ton of reads before I run my SQL to know how to run my SQL. Where’s my data, for example?

[1] https://www.voltdb.com/blog/2015/04/01/foundationdbs-lesson-...

Re: What to Expect in CockroachDB 1.0

#33

Post by si13 »

BramG wrote: post #31
si13 wrote: post #29

Is .net core a second class citizen? Why dont you care c# clients (npgsql)

.Net wasn't a priority due to our very limited resources. We will be expanding the number of drivers and ORMs greatly over the next while. That being said, I tested npgsql a few days ago and it worked perfectly. Nothing too extensive, just created a db, 2 tables, inserted some data and did a join. So please give it a shot and if it doesn't work, file issues and we'll address them. (disclosure: I work at cockroach lab…

Thank you. Also this page needs an update https://www.cockroachlabs.com/docs/install-client-drivers.ht...

Re: What to Expect in CockroachDB 1.0

#34

Post by manigandham »

SilasX wrote: post #30
adrift wrote: post #18

Earlier quoted context omitted.

What's wrong with it?

Are you asking about rust? Not the parent but: Because the term has universally negative connotations: I don't like equipment that's rusted. I don't like when joints have rusted into position. I don't like getting rusty at skills. I don't like rusty pipes or rust getting into drinking water. I don't like turning on a faucet and seeing the color of rust come out. I know it's not 100% rational, but the feeling of revul…

What does it matter what the average person thinks? Are they making database/language decisions for your product?

You can argue that potential managers might be influenced but it should be easy enough to put the merits of the product before the name itself.

Re: What to Expect in CockroachDB 1.0

#35

Post by manigandham »

CockroachDB is an exciting development and we fit right into the underserved use-case of multi-regional databases. If it had JSON columns we would put it into production today.

Google's Spanner is pretty great too but also missing any json columns and too locked into GCP. We're also looking at using a JanusGraph on top of ScyllaDB to get better querying ability with strong multi-region access.

Re: What to Expect in CockroachDB 1.0

#36

Post by manigandham »

misterbowfinger wrote: post #23
subsidd wrote: post #9

I am a database newbie, what are it's pros and cons over postgres?

On a similar note, how does this compare against Citus?

Citus is offered as a Postgres extension, primarily allowing you to run a cluster of postgres servers together as a single logical database with tables automatically sharded by a key of your choosing.

Slightly limited but distributed SQL queries can run across all nodes to speed up access or scan lots of data - or you can choose something like a customer_id to shard all the tables the same way so that all data for that customer would be on the same node, allowing for full SQL syntax and features on data of that node (because it would just be a regular postgres server).

For a data-warehouse/fast-realtime scenario, I would also recommend MemSQL although it is proprietary.

Re: What to Expect in CockroachDB 1.0

#38

Post by macspoofing »

manigandham wrote: post #34
SilasX wrote: post #30

Earlier quoted context omitted.

Are you asking about rust? Not the parent but: Because the term has universally negative connotations: I don't like equipment that's rusted. I don't like when joints have rusted into position. I don't like getting rusty at skills. I don't like rusty pipes or rust getting into drinking water. I don't like turning on a faucet and seeing the color of rust come out. I know it's not 100% rational, but the feeling of revul…

What does it matter what the average person thinks? Are they making database/language decisions for your product? You can argue that potential managers might be influenced but it should be easy enough to put the merits of the product before the name itself.

This isn't really a rational discussion. We're complaining about a name.

Re: What to Expect in CockroachDB 1.0

#39

Post by SilasX »

manigandham wrote: post #34
SilasX wrote: post #30

Earlier quoted context omitted.

Are you asking about rust? Not the parent but: Because the term has universally negative connotations: I don't like equipment that's rusted. I don't like when joints have rusted into position. I don't like getting rusty at skills. I don't like rusty pipes or rust getting into drinking water. I don't like turning on a faucet and seeing the color of rust come out. I know it's not 100% rational, but the feeling of revul…

What does it matter what the average person thinks? Are they making database/language decisions for your product? You can argue that potential managers might be influenced but it should be easy enough to put the merits of the product before the name itself.

Would you see a problem with [obscenity]DB? Or SyphillisDB? PubesDB?

If so, then you agree the name matters, "and we're just haggling over the details."

Re: What to Expect in CockroachDB 1.0

#40

Post by petermattis »

elvinyung wrote: post #32
didip wrote: post #5

Any newer Jepsen test since this one: https://jepsen.io/analyses/cockroachdb-beta-20160829 Also, how's the performance nowadays?

I noticed that the question on performance was ignored, but I think it's worth noting that FoundationDB died on exactly the same beach. [1] I'm not extremely familiar with the CockroachDB architecture (other than "it's kinda like the F1/Spanner/Bigtable stack"), but I suspect that there are some commonalities. For example, CockroachDB's Bigtable-style two-level range indexing means you could run into exactly this pro…

(Cockroach Labs co-founder here)

CockroachDB also stores SQL metadata inside of the KV store, but that metadata is also gossiped around the cluster (i.e. it is replicated to every node) so that SQL execution almost never has to read it from the KV store. Handling changes to this SQL metadata is challenging and required a design [1] that is unable to take advantage of the easy correctness of simply doing reads from the KV store on every operation.

[1] https://github.com/cockroachdb/cockroach/blob/master/docs/RF...

Post reply on HN