3 ms·
And this is why Google wrote Spanner. I think cockroachdb tries to solve the same problems. If you need ACID compliance and you need a lot of it, everywhere,
by benlivengood 5y ago
And this is why Google wrote Spanner. I think cockroachdb tries to solve the same problems.
If you need ACID compliance and you need a lot of it, everywhere, all the time, now there are better options than giant Sun/IBM boxes.
Databases are not the problem.
- tyingq 5y agoIt's still a fairly new thing for people outside of Google. It's been a few years, so I imagine it's better now...but when I tried CockroachDB, it was pretty easy to trigger horrible write latency. Bad enough to be a non-starter.
- namibj 5y agoWhich version, and what networking did you have between the cluster nodes?
- tyingq 5y agoI don't recall other than it was before 2.x, but I don't think it's terribly important. The cockroachdb folks were very transparent about it, including a couple of major re-works to address performance. Here's a blog post about one of them: https://www.cockroachlabs.com/blog/2-dot-0-perf-strides/ https://www.cockroachlabs.com/blog/2-dot-0-perf-strides/ I was just trying to say that a stable, high performance SQL database with distributed writes is a fairly new thing.
- CRConrad 5y ago> If you need ACID compliance and you need a lot of it, everywhere, all the time, now there are better options than giant Sun/IBM boxes. Oh I dunno, I'd still say most claims to be "better" at data integrity with performance, and a lot of it than a good old zOS mainframe with a soundly designed DB2 database on it are [Citation needed]-class... But yeah, databases certainly aren't the problem here.