title: NOsql Vs Mysql - Going schemaless with Cassandra
body: <p>Here are the facts:</p>
  
  <ul>
  <li>We have a lot (L O T) of data coming in everyday.</li>
  <li>Each file we receive is in a csv format and while there are a couple of headers that reoccur more often than others, there is not really a standard.</li>
  <li>The normalization of each file to be uploaded into a mySQL database is highly time consuming and often pushes us to change the schema (new field appeared in on file that was not existing before..).</li>
  <li>While the primary key is unique, anything else can be duplicated</li>
  <li>These are customers records (i.e.: email,firstname,lastname,city,state,address...etc)</li>
  <li>We could have multiple emails for the same individual ..</li>
  <li>We read 70% of the time and we write 30% of the time</li>
  <li>Scalability could be a concern but it is not right now, though availability is key</li>
  <li>Speed is what we are looking for. Mysql is too slow to answer queries where tables are over 50 million records. Even well optimized we have too many speed issue. Breaking down the tables has become an organizational concern. Schema less noSQL seemed attractive. What would you recommend, what did you implement? (Please do not answer to optimize mysql .. pointless and off topic)</li>
  </ul>
  
  <p>--</p>