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

CockroachDB 1.0

cockroachlabs.com

Post reply on HN
Print view View original

271–280 of 366 posts

Re: CockroachDB 1.0

#271

Post by genkaos »

SilasX wrote: post #264
genkaos wrote: post #197

Earlier quoted context omitted.

I'm a spaniard and mongo is an insult. [removed unnecessary snarky comment]

Okay, there are separate issues going on here; let me try to clarify: Is "mongo" the equivalent of English "retard", in terms of being a low-class insult that invokes a visceral reaction among the majority of the population? I didn't believe that at first; if so, why didn't anyone ever put it in Wikipedia? English has "retard" (in the pejorative sense): https://en.wikipedia.org/wiki/Retard#Other_uses And why doesn't…

And that's my point. You're only offended because it's in english (and that's fair). But no matter what name you use, it will offend someone. CucarachaDB will fly under the radar.

Maybe you have to be culturally immersed to know those things. Mongo, mongol and mongólico are the terms you should research.

Re: CockroachDB 1.0

#272

Post by dang »

newsat13 wrote: post #160

Very disappointed with HN turning into a 4chan/reddit style trolling board about the name. Guys, we get it that you don't like the name. Can we please stop bike shedding and move on? The people at cockroachdb have obviously seen all your messages but decided it's worth keeping the name. What more is there to talk about? Why not talk about the relative technical merits of this DB?

> Can we please stop bike shedding

Unfortunately this is a version of the thing it's trying to stop, as is plain from the below. These balls of mud are immune to negation; they laugh at it and grow stronger.

Re: CockroachDB 1.0

#273

Post by nvarsj »

irfansharif wrote: post #270
nvarsj wrote: post #267

Earlier quoted context omitted.

I don't really get why you would build a distributed database with dependency on wall time (unless you're Google and can stick atomic clock HW on every node). Why not use vector clocks? Am I missing something?

the section on lock-free distributed transactions on our design document[1] should answer your question, specifically the sub-section on hybrid logical clocks. [1]: https://github.com/cockroachdb/cockroach/blob/master/docs/de...

Thanks! Interesting. http://www.cse.buffalo.edu/tech-reports/2014-04.pdf is the relevant paper on hybrid logical clocks, linked in the faq.

Re: CockroachDB 1.0

#274

Post by arjunnarayan »

steveklabnik wrote: post #203
arjunnarayan wrote: post #182

Earlier quoted context omitted.

This is more my personal opinion, and perhaps more revealing my ignorance on the existing equivalent tools in the Rust ecosystem, but here is a list of some of the Go tools we use when developing CockroachDB: 1. gofmt and goimports really helps enforce a single uniform style. We don't really care what the style is, as long as it's consistent across our 30 engineers and 200k lines of code. We have hand-rolled more Coc…

Thank you so much for the thorough answer! This is stuff we're always working on, so it's helpful to know about this stuff. Since you're not actively looking, I won't go into all the details, but if you ever are in the future, happy to give you a rundown of the state of the art whenever that is :)

Thank you as well! I will almost certainly reach out to you about this at some point!

Re: CockroachDB 1.0

#276

Post by SilasX »

genkaos wrote: post #271
SilasX wrote: post #264

Earlier quoted context omitted.

Okay, there are separate issues going on here; let me try to clarify: Is "mongo" the equivalent of English "retard", in terms of being a low-class insult that invokes a visceral reaction among the majority of the population? I didn't believe that at first; if so, why didn't anyone ever put it in Wikipedia? English has "retard" (in the pejorative sense): https://en.wikipedia.org/wiki/Retard#Other_uses And why doesn't…

And that's my point. You're only offended because it's in english (and that's fair). But no matter what name you use, it will offend someone. CucarachaDB will fly under the radar. Maybe you have to be culturally immersed to know those things. Mongo, mongol and mongólico are the terms you should research.

>And that's my point. You're only offended because it's in english (and that's fair).

I specifically said I would be sensitive to the offense it would cause in other languages, at least the major ones.

Re: CockroachDB 1.0

#277

Post by lima »

jordanlewis wrote: post #241
octernion wrote: post #184

Earlier quoted context omitted.

what's the story for change data capture with CockroachDB? Postgres 9.4 added logical replication, which is incredibly useful for this use case. Also, we use JSONB fairly extensively -- I see the tracking issue here https://github.com/cockroachdb/cockroach/issues/2969 but no movement.

Regarding change data capture, please see Arjun's answer: https://news.ycombinator.com/item?id=14309173

Make sure to take a look at Debezium: http://debezium.io/

It's a really solid CDC framework which has connectors for PostgreSQL, MySQL and MongoDB.

Re: CockroachDB 1.0

#278

Post by ww520 »

sixdimensional wrote: post #138

How does Cockroach efficiently handle the shuffle step when data is on many nodes on the cluster and has to move to be joined? Does Cockroach need high capacity network links to function well? I always see companies making the claim of linear speedup with more nodes but surely that can't be the case if the nodes are geographically disjointed over anything less than gigabit links? Perhaps linear speedup with more node…

15 years ago I was working on a similar distributed DB product. At the time, the idea was to send the query execution plan to each node to execute any filtering criteria to trim down the candidate row set. Then compute a Bloom Filter on the joining keys on the node with the largest candidate set (using some heuristic statistics), ship the Bloom Filter to other nodes with smaller data set to greatly reduce the non-matching rows. The rows survived the Bloom Filter are highly likely joinable and are shipped back to the main joining node to perform the final join. Bloom Filter is the perfect compromise between size and speed.

I'd imagine CockroachDB is doing something similar for distributed join.

Re: CockroachDB 1.0

#279

Post by lima »

jhall1468 wrote: post #208
zzzcpan wrote: post #130

Earlier quoted context omitted.

"getting foolproof HA straight out of the box" This is a minimal requirement for any modern database.

No, HA straight out of the box is a minimal requirement. Foolproof HA is not a requirement, since neither MySQL or Postgres offer "easy" HA setup.

Galera cluster works "out of the box", that might be the closest SQL competitor in that regard.

Re: CockroachDB 1.0

#280

Post by nickpsecurity »

zzzcpan wrote: post #257
nickpsecurity wrote: post #227

Earlier quoted context omitted.

I support the default on consistence the way you posed it. Main reason is safe-by-default construction has proven more effective for average programmer over decades. The other approach caused many disasters.

Meh, this is just pr, nothing is safe-by-default. It's not actually true that people eventually assume strong consistency, because eventual consistency forces certain stricter way of thinking about the state and time, kind of functional, you just can't escape it. It's strong consistency that lets you get sloppy, while making you forget how not simple it is. It only exists inside the system and if you have clients fro…

Google disagreed on that last part. Their bright engineers kept screwing up with eventual consistency. It's why they built Spanner in the first place followed by F1. So did customers of FoundationDB and Cochroach despite free solutions available for eventual consistency.

So, Im not seeing it so clear cut in favor of eventual consistency.

Post reply on HN