I should also have noted that proper application and schema design (partitioning, sharding, etc…) will go much farther towards reliability, performance, and recoverability than swapping storage engines.
Hi Geogrelorch,
So in my scenario what is best suggested to go with partitioning or sharding? I read a lot of issue with sharding when reading up the data cause it involves multiple machines. So in my scenario like 300 million data per month what is the best schema design to go with ?
This is not a question that I can answer, there are entirely too many variables involved in your workflow and desired response times. It sounds like you could use some help from a real DBA or architect, I am a server developer.
Hi Georgelorch,
Thank you. I really appreciate your help and answer for the rest.