title: Distributed database use cases
body: <p>At the moment i do have a mysql database, and the data iam collecting is 5 Terrabyte a year. I will save my data all the time, i dont think i want to delete something very early.
  I ask myself if i should use a distributed database because my data will grow every year. And after 5 years i will have 25 Terrabyte without index. (just calculated the raw data i save every day)</p>
  
  <p>i have 5 tables and the most queries are joins over multiple tables.
  And i need to access mostly 1-2 columns over many rows at a specific timestamp.</p>
  
  <p>Would a distributed database be a prefered database than only a single mysql database?</p>
  
  <p>Paritioning will be difficult, because all my tables are really high connected.</p>
  
  <p>I know it depends on the queries and on the database table design and i can also have a distributed mysql database. 
  i just want to know when i should think about a distributed database.
  Would this be a use case? or could mysql handle this large dataset?</p>
  
  <p>EDIT:</p>
  
  <ul>
  <li><p>in average i will have 1500 clients writing data per second, they affect all tables.</p></li>
  <li><p>i just need the old dataset for analytics. Like machine learning and
  pattern matching.</p></li>
  <li>also a client should be able to see the historical data</li>
  </ul>