> durable and rich data model. It will not provide your high performance, > especially reading performance is poor.
Note that for several realistic work-loads, the above claim is most definitely wrong. For example, for large databases with a mix of insertions/deletions (so that the MySQL case doesn't boil down to append-only (and even then I'm discounting indexes)), you might achieve orders of magnitude faster performance with Cassandra than with MySQL. In other cases, Cassandra is slower. As always, it depends. But the implication that performance is not a reason to use Cassandra is not reflective of reality. This is especially true for large data sets (and by that I mean "amount of data on a single machine"). -- / Peter Schuller