Right, I don't need to store the list of movies in the database.
Here is the scenario:
1 - The user search a movie by the name
2 - I render a list of movies with various informations (like director,
actors) fetched from the external API. And yes I need the list to be
fresh every time.
3 - The user pick a movie from the list
4 - I store the informations, of the movie the user choose, in the
database so the user can consult these informations latter.
I'm stuck on how to achieve the step 4.
- I could make another request to the API for the selected movie but I
want to minimize API's requests.
- I could extract movie details from the view. I don't know if it's
truly possible but I doesn't seem quite right anyway.
- I could store the movie details from the step 2 and delete all
informations I don't need latter.
- I could use volatile memory to store movie details from step 2, and
then store the movie the user choose in the database.
I thought the latest option was the more appropriate.
I hope I'm more clear this time.