Yes, cassandra's big win is that once you get your data and applications
adapted to the platform, you have a clear path to very very large scale and
resiliency. Um, assuming you have the dollars. It scales out on commodity
hardware, but isn't exactly efficient in the use of that hardware. I like
to
I suspect you're approaching this problem from the wrong side.
The decision of MySQL vs Cassandra isn't usually about performance, it's
about the other features that may impact/enable that performance.
- Will you have a data set that won't fit on any single MySQL Server?
- Will you want to write
Hello Oliver,
The first thing that I check when seeing if a workload will work well
within Cassandra is by looking at it's read patterns. Once the read
patterns can be written down on paper, we need to figure out how the write
patterns will populate the required tables. Since you know enough about
Hello,
Thanks for all the responses.
I do know some SQL and CQL, so I know the main differences. You can do
joins in MySQL, but the bigger your data, the less likely you want to do
that.
If you are a team that wants to consider migrating from MySQL to
Cassandra, you need some reason t
I’m not sure there is a fair comparison. MySQL and Cassandra have different
ways of solving related (but not necessarily the same) problems of storing and
retrieving data.
The data model between MySQL and Cassandra is likely to be very different. The
key for Cassandra is that you need to model
