title: ease of scaling mongodb vs mysql
body: <p>I am creating a Grails application that is the backend for a mobile application. It is  currently deployed on Amazon EC2. It persists data to a mysql database. One instance currently pointing to the database. I plan to deploy multiple instances of the app behind a load balancer and eventually have read requests go to slave instances of the db. We plan to release in the coming months and have a beta group of a couple of thousand users. It is more read intensive than write. </p>
  
  <p>We have looked into using mongodb instead of sql and see it as a good solution. </p>
  
  <p>Not having a lot of experience scaling mysql ( or mongodb ) would it be easier to scale mongodb since it has features such as auto sharding. ( Looking for thoughts from people who have done both )  I am of thinking it will be easier to switch to mongodb now rather than be in 'production' and having to migrate. </p>
  
  <p>Thoughts?</p>