I am designing a movie-recommendation iOS app based on Movie Awards. It would only show movies that were nominated to awards, and the user would be able to filter data by award (Oscars, Golden Globe, etc), by year, by categories, etc.
That would require a database to store all the award and movie data. The movie data will be retrieved from The Movie Database API, but I still need to store some of it (TMDB id, name, year, poster, etc) to create the relationship of each movie with the specific awards it's in.
Therefore I need an "awards" database. It should store award information, dates, categories, nominees, winners, etc.
I was thinking of going the easy way (for me!) and use SQLite for that. It is a very predictable database, and will be updated a few times a year only.
But then I got lured into the NoSQL discussion.
As I am planning to, on a v2.0, allow users to save movies in a watchlist, or mark as watched, I though this would be a great use for NoSQL?
Please help! What would you do? Use both? focus on SQL or NoSQL only?