search

staab / js-allonge

Repository for collaboration on the project for the Javascript Allonge group 2014
MIT License
1 stars 3 forks source link

Build TMDB api #4

Open staab opened 10 years ago

staab commented 10 years ago

Basically a wrapper that fits our use-cases, abstracts away HTTP, and includes a cache.

We'll have to get ourselves an api key. https://www.themoviedb.org/

staab commented 10 years ago

The changes endpoint could be useful for managing our cache

cr-walker commented 10 years ago

That looks great: as long as we scan the changes api every few days and update cache, we should be able to keep them synced.

I'm going to suggest that the cache belongs in mongodb since it does a great job of keeping frequently used documents in memory anyways. That or redis. Anyways, see my thoughts on how to structure the db here: #5.

austinstorm commented 10 years ago

I agree, MongoDB makes sense.