title: Movies database use SQL or NoSQL .net
body: <p>I need to write a media application which stores movie/tv shows preferences/favorites for each user.I need help in deciding whenever to user a NoSql or not. </p>
  
  <p>The application will have a huge database of movies/tv shows metadata, similar to imdb.com, rottentomattoes etc. This data is read-only for the user, only admins are expected to edit the movies content. I also plan to expose this data through odata.</p>
  
  <p>My gut tells me that i should use NoSql for at least storing the media data, but I'm afraid that i will lose a lot of development productivity tools (Entity Framework, designers.. etc).</p>
  
  <p>I am also worried about NoSql and data duplication (e.g each movie has a list of genre which would be duplicated in each k/v or document (depends on which nosql db i choose))</p>
  
  <p>My next feature would be to provide an autocomplete of movie titles so i need to keep that in mind too.</p>
  
  <p>Has anyone done something similar with this? Are my worries correct?</p>