News for hackers. Stuff that matters.
Re:Jepsen: YugaByte DB 1.1.9 by gigatexal on Tuesday March 26, 2019 @05:37PM (#19496273)
We use cockroachDB in production and before that we were on MySQL and as of yet we don’t have a specific usecase where we use serializable transactions. Snapshot isolation or even read committed is just fine. So I don’t think it’s absolutely necessary
Re:Jepsen: YugaByte DB 1.1.9 by gigatexal on Wednesday March 27, 2019 @01:00AM (#19498281)
To be clear there’s no way around serializable transactions in cockroachDB. We have had to adapt our monolith to it (we’re thinking of ways to make it more nimble by breaking out services etc). But the point I was making was that we had MySQL for a while and never ran into issues with its isolation levels until it stopped scaling. Instead of vitess or some other MySQL system we went with cockroach after finding vitess didn’t fit us — too complicated and too many moving parts. CockroachDB just works. Also moving to k8s adds complexity too for a monolith built and run on VMs. But so far so good. Cockroach runs fast and is performant given production queries. And ops is happy because it self heals.
Re:Jepsen: YugaByte DB 1.1.9 by redwood on Wednesday April 03, 2019 @10:25PM (#19568867)
First time I've heard about a production use case. Care to share any details?