> can handle most workloads. They really shine for read heavy workflows that can tolerate a stale read every once in a while. If on top of that you have reason

> can handle most workloads. They really shine for read heavy workflows that can tolerate a stale read every once in a while. If on top of that you have reasonable shard-ability you get near infinite scalability. While that might cover a large portion of the database usage landscape, I'd hesitate to call it most. There's a reason OLTP was coined as an acronym--it's a pattern that comes up a fair bit.