8
6 Comments

Store API data

I am using an API the tmdb api for movies to be specific. I wish to store the api data in to a database so I have to make less api queries, however I am not sure if there is legal restrictions and yes this is for a commercial app.
If I can't store the data in the database would that mean i would have to curate all the movie information my self then store in a database?

on August 30, 2020
  1. 2

    What is the difference between a commercial API and a developer API?
    A commercial API is for commercial projects and a developer API is for developers. Your project is considered commercial if the primary purpose is to create revenue for the benefit of the owner.
    https://www.themoviedb.org/faq/api

    I have a feeling you should be paying, it's their terms, IDK... not reading everything and not a legal consult...
    There isn't a generic how API should be used you should see the specific terms they claim..

    Generally for storing the data, you either reconstruct the data module (might just find full DB offers) or cache the call results with something like Redis which is simple
    If key existent, return key if not do call and store key

  2. 1

    It is surely tough to build a advanced shopify clone from scratch. In my opinion you ought to focus on a gap marketplace or sell a Bape clothing to shopify like volkan said.

  3. 1

    How can we use the API data for single page? I want to test it for the ecommerce store, you can see here https://malekgreenhouse.ir/

  4. 1

    Wouldn't a simple expiring cache do the trick? They don't rate limit https://developers.themoviedb.org/3/getting-started/request-rate-limiting so the only reason to try to have the data yourself is if you are doing complex queries of some sort across movies.

    1. 1

      I do plan only allowing users to favourite movies and also the Web app will be able to recommend movies to users. So i think storing in a dB might be best. What do you think?

      1. 1

        Depends - are the recommendations only based on user's favourites? If so you will of course already have favourite data in your database. Then this just becomes a performance problem and the cache would solve that. Otherwise some aspect of the data you are using might change over time and you don't want to be maintaining tmdb yourself.

        I'm afraid without knowing what you are doing I can't really advise more. To complicate things even more even if you need a cache you don't necessarily need a centralized one. Uclusion caches all user data in IndexedDB.

Trending on Indie Hackers
I spent $0 on marketing and got 1,200 website visitors - Here's my exact playbook User Avatar 67 comments Veo 3.1 vs Sora 2: AI Video Generation in 2025 🎬🤖 User Avatar 30 comments I built eSIMKitStore — helping travelers stay online with instant QR-based eSIMs 🌍 User Avatar 20 comments 🚀 Get Your Brand Featured on FaceSeek User Avatar 19 comments Day 6 - Slow days as a solo founder User Avatar 16 comments Why I'm Done Juggling 10 SaaS Tools (And You Should Be Too) User Avatar 8 comments