21–30 of 75 posts
Looks neat! I noticed this: CockroachDB is not suitable for use cases involving joins (yet) Well guys, that's the kicker. If you've got joins, you've got SQL. The selection language isn't so important if you can't do set relations. I'm sure you're going to rock this. Can't wait to see how you do it!
Been watching this DB for a while. Glad to see it enter beta. I recommend including https://github.com/mauricio/postgresql-async on https://www.cockroachlabs.com/docs/install-client-drivers.ht... (it's my favorite Postgres client, it's very fast).
Nice seeing a new SQL database but who comes with with names like this?
I've been watching this project for a while. This is very cool. I think they've made a lot of very good design choices.† Oh, and the client drivers page should probably also list pgx ( https://github.com/jackc/pgx ), which is a nice, fast PostgreSQL client that doesn't use the not-as-nice database/sql package. ___ † The name being the only exception; I don't have bug phobia at all, but cockroaches are just icky.
This is one of the most exciting DB's coming into the world, and I've had a lot of fun watching progress from the sidelines! Keep kicking ass!
> This is one of the most exciting DB's coming into the world, and I've had a lot of fun watching progress from the sidelines! I'm going to have to disagree. The German HyPer DBMS has a lot more interesting ideas. Cockroach is just distributed MVCC from the 1980s on top of a key/value store. MemSQL also has a new LLVM architecture written by the HipHop VM inventor that they poached from Facebook.
Yeah. Not so much. I can't think of anything that used the 2 phase transactions over independent consensus groups (aka spanner) pattern from the 80's. Likewise there was nothing like Yabandeh transactions in 1980 because no one actually understood serializable snapshot isolation then (but several projects mistakenly thought they had, which was Yabandeh et all's entire motivation).
HyPer is neat work, but that it is interesting does not mean CockroachDB is not also.
Full disclosure: I work for a non-competing (EC vs SC) database - which also has an ugly name "gunDB". Super excited to hear about CockroachDB's progress - and their decision to add SQL support I think was smart. However, I can't go without critiquing their marketing of "Scalable" and "Strongly Consistent", especially when they reference horizontal scaling. Strongly Consistent systems bottleneck around a centralized…
The rest of your comment ignores a couple decades or so of very extensive research into scalable distributed transactions.
Design documentation is here if you care to read it: https://github.com/cockroachdb/cockroach/blob/master/docs/de...