ScyllaDB is Moving to a New Replication Algorithm: Tablets

Very similar to how BigTable[1] works under the hood which was built ~20 years ago.<p>[1] <a href="https:&#x2F;&#x2F;static.googleusercontent.com&#x2F;media&#x2F;research.google.com&#x2F;en&#x2F;&#x2F;archive&#x2F;bigtable-osdi06.pdf" rel="nofollow noreferrer">https:&#x2F;&#x2F;static.googleusercontent.com&#x2F;media&#x2F;research.google.c...</a>

This is the right move for Scylla. Overall, looks similar to YugabyteDB that distirbutes data by sharding tables into tablets as well. The cluster monitors the cluster size (number of nodes) and the size of each tablet (data volume), and adds new tablets or re-shards large ones automatically:<a href="https:&#x2F;&#x2F;docs.yugabyte.com&#x2F;preview&#x2F;architecture&#x2F;docdb-sharding&#x2F;tablet-splitting&#x2F;#automatic-tablet-splitting" rel="nofollow noreferrer">https:&#x2F;&#x2F;docs.yugabyte.com&#x2F;preview&#x2F;architecture&#x2F;docdb-shardin...</a>

This sounds a lot like ranges in CockroachDB. Anyone familiar with the deep details to highlight the differences?

Moving from Vnode-based replication to tablets to dynamically distribute data across the cluster

Tablets remind me of vitess

Would be nice if the deployment story became a bit more like CockroachDB too.

This sounds like partitions in DynamoDB