4 ms·
Yeah, if you can wait another year or two, something like CockroachDB [1] might fit the bill. That is a database that is distributed from the start. So you (t
by ansible 10y ago
Yeah, if you can wait another year or two, something like CockroachDB [1] might fit the bill. That is a database that is distributed from the start. So you (theoretically) won't have to worry as much about individual datacenter failures, and scaling.
[1] http://www.cockroachlabs.com http://www.cockroachlabs.com
- StreamBright 10y agoI usually wait 5 years with a database/datastore after it goes GA before consider it for anything. Looks promising though.
- ansible 10y agoYes, I've liked the design from the very start, and they've got a nice group of people working on it. It's supposed to go into a 1.0 release this year. I'll probably try it out on a service where I'm writing simultaneously to two different databases, one local and one distributed. And then log any issues where I see an inconsistency. I won't be relying on it for a while for anything critical.
- brightball 10y agoWhat about Couchbase?
- StreamBright 10y agoWe had serious operational issues with Couchbase and some funny developers where always ready to answer our tickets with "works on my laptop". One we had 1.3 billion documents in the cluster and it became unstable and we had to delete all of the data to bring the service back online. Luckily we used S3 as the source of truth based on the operational characteristics of CB. I would not recommend it for anybody who is not ready for massive dataloss and continuous operational issues. Some of these might be been fixed in the meanwhile though.
- throwaway91111 10y agoCouchbase appears to require failover as it has authoritative servers (three, it looks like?). CockroachDB should scale linearly with cluster size, meaning failover isn't a thing--it just struggles until you give it more CPU/disk/mem/what have you.