Aurora's horizontal scaling doesn't depend on sharding at all- read-scaling uses read-replicas, and multi-master write-scaling uses a hierarchical conflict-reso

Aurora's horizontal scaling doesn't depend on sharding at all- read-scaling uses read-replicas, and multi-master write-scaling uses a hierarchical conflict-resolution strategy [1]. On 'beating Aurora', my point was that comparing a 30-node CockroachDB cluster against a single-node Aurora benchmark and concluding that Cockroach is 'more scalable' is disingenuous, considering Cockroach 2.0 just reached GA, and Aurora multi-master has been available in preview since November and will likely also reach GA in coming months. Once Aurora multi-master reaches GA, I'll look forward to a more direct comparison of an Aurora multi-master cluster against a similarly-sized CockroachDB cluster. [1]: https://www.slideshare.net/AmazonWebServices/deep-dive-on-the-amazon-aurora-mysqlcompatible-edition-dat301-reinvent-2017/36 https://www.slideshare.net/AmazonWebServices/deep-dive-on-th...