Find a good API for movie trailer data

[bshyong]

We need poster images, description, and trailer content.

• http://www.omdbapi.com/

We'll query this from our API server to preprocess the response however we see fit before sending to our front-end service to consume.

[chkche1]

While I'm working on a prototype for the backend, the data model design problem immediately surfaces itself.

We definitely want a DB for this project. The DB schema can served as the internal model. The frontend should only get the external model (we can defined the model in another package say called TrailerZooClientModel), essentially the view model for most cases.

Happy to discuss more on this. Here's an attempt to define the tables for a v1 product

MOVIES table

• movie id
• title
• description

IMAGES table

• movie id
• image path*

VIDEOS table

• movie id
• video path*
• DB should store an URL or a file system path for media content instead of a blob. Depending on what's available, we can try different things.

Based on what I'm seeing, dropwizard should allow me to quickly come up with a functional prototype for our server.

[bshyong]

Great; this is solid. File paths are good since we could easily use S3 for storage of images and movies. In case we can get additional data about a movie besides title and description, how do you think we should handle it?

the other data that we could potentially store is

• director
• release date
• actors/actresses

One way to do this is to store a JSON blob in an 'extra attributes' column—if we want to have relational data around this in the future we can always pull out the info from the blob and write it to explicit db columns

[bshyong]

Add me to the repo when you set one up! I think we can use CircleCI for integration—it's pretty good and should have Java support https://circleci.com/docs/language-java

[chkche1]

Cool. I'm going to try to set up something using postgreSQL and good point on storing director, release date, actors/actresses.

Love to explore CircleCI!