Out of curiosity, does DynamoDB autoscaling allows you to exceed the partition limits (e.g. push more data than it is allowed for some outlier heavy partitions) ? If yes, it can be interesting (I guess DynamoDB is doing some kind of rebalancing behind the scene). If no, it's just an artificial capping figure they increase to cope with spikes in throughput
On Mon, Dec 9, 2019 at 9:35 PM Carl Mueller <carl.muel...@smartthings.com.invalid> wrote: > Dynamo salespeople have been pushing autoscaling abilities that have been > one of the key temptations to our management to switch off of cassandra. > > Has anyone done any numbers on how well dynamo will autoscale demand > spikes, and how we could architect cassandra to compete with such abilities? > > We probably could overprovision and with the presumably higher cost of > dynamo beat it, although the sales engineers claim they are closing the > cost factor too. We could vertically scale to some degree, but node > expansion seems close. > > VNode expansion is still limited to one at a time? > > We use VNodes so we can't do netflix's cluster doubling, correct? With > cass 4.0's alleged segregation of the data by token we could though and > possibly also "prep" the node by having the necessary sstables already > present ahead of time? > > There's always "caching" too, but there isn't a lot of data on general > fronting of cassandra with caches, and the row cache continues to be mostly > useless? >
