title: Architectural design of write heavy application
body: <p>I am dealing with live tracking system where one device can push around 2 million GPS points every year (i.e 1 point every 5 seconds, operating for 8 hours over 365 days). If this operates on a global scale with thousands of devices, this results in billions of records per year.</p>
  
  <p>I know SQL Server can handle it. But I need to be able to perform live tracking with thousands of devices performing concurrent writes. It works fine with a few devices but I can see this being CPU intensive when I open lots of tracking sites. </p>
  
  <p>I am planning to try:</p>
  
  <ul>
  <li>Mongo DB</li>
  <li>Socket approach with kazzing.</li>
  </ul>
  
  <p>Any alternative suggestions?</p>