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?

Reply via email to