title: Limits to move from Sql to NoSql Database
body: <p>We are facing performance related issues in our current MySQL DB. Our application is pretty heavy on a few tables ~20. We run lot of aggregation queries on this table as well as writes. Most of our teams are developers and we don't have access to a dba which might help in retuning our current db and make things work faster.</p>
  
  <p>Moving to NoSql is an option. But seriously thinking what are the higher limits in terms of </p>
  
  <ul>
  <li>Volumes (Current volumes per day ~50GB)</li>
  <li>Structured or Raw Data? (Structured Data)</li>
  <li>IO stats on DB - ( Current rate is 60 KB/Sec)</li>
  <li>Record writes - (now 3000 rows/sec)</li>
  </ul>
  
  <p>Question arise</p>
  
  <ul>
  <li>Is 50GB is high enough to consider NoSql? Some documentation recommends more than a TB</li>
  <li>The data should be raw data, which can be further processed to get structured and use in application</li>
  <li>MySql scales out at 3000 rows/secs, not sure MySql can be further tuned</li>
  </ul>
  
  <p>HBase seems to be promising for Analytic application.</p>
  
  <p>Would like to get some guidelines on limits of RDBMS one can think of moving to NoSQL</p>