Hi Oliver, Few years back I had a similar problem where there was a lot of data in MySQL and it was starting to choke. I migrated data to Cassandra, ran benchmarks and blew MySQL out of the water with a small 3 node C* cluster. If you have a use case for Cassandra the answer is yes, but keep in mind that there are some use cases like relational problems which can be hard to solve with Cassandra and I tend to keep them in relational database. That being said, I don't think you can benchmark these two head to head since they basically solve different problems and Cassandra is distributed by design.
Best, Matija On Mon, Mar 12, 2018 at 9:27 PM, Gábor Auth <auth.ga...@gmail.com> wrote: > Hi, > > On Mon, Mar 12, 2018 at 8:58 PM Oliver Ruebenacker <cur...@gmail.com> > wrote: > >> We have a project currently using MySQL single-node with 5-6TB of data >> and some performance issues, and we plan to add data up to a total size of >> maybe 25-30TB. >> > > There is no 'silver bullet', the Cassandra is not a 'drop in' replacement > of MySQL. Maybe it will be faster, maybe it will be totally unusable, based > on your use-case and database scheme. > > Is there some good more recent material? >> > > Are you able to completely redesign your database schema? :) > > Bye, > Gábor Auth > >
