I'd be interested in hearing:
- the backup story
- the replication/failover story
- horizontal scaling story (is it plug and play)
I'd be interested in hearing:
- the backup story
- the replication/failover story
- horizontal scaling story (is it plug and play)
Your other questions are better answered on the blog post, but quickly:
* CockroachDB core comes with a `dump` command to backup your databases. CockroachDB Enterprise has blazingly fast _incremental_ cloud backup and restore, the kind that you might want for a very large deployment.
* Replication is managed under the hood by sharding the data into many ranges that are each 64mb in size. Each range is replicated using Raft, and if a node goes down, the other replicas scattered across the cluster seamlessly take over and upreplicate a new replica to "heal" the cluster.
* The horizontal scaling is indeed plug and play - just add more nodes to the cluster and they'll automatically rebalance replicas across the cluster with no downtime and no additional configuration.
As for our backup story, our doc page[2] on the subject should shed more details.
[1]: https://www.cockroachlabs.com/docs/build-a-ruby-app-with-coc...