The current Search API supports results for partial queries as well (e.g: "Incep" provides "Inception" as result). So I was wondering if I could send an API call for each key press in the search field for a user?
Essentially, it calls for inc, ince, incep, incept etc. as the user types out the name, so they get updated and more accurate results with each letter. This basically means I'm sending a separate GET sent with each keystroke.
Will I hit the API rate limiter or something if I use this? Even if my app has 5k concurrent users, will I not hit any API wall due to rapid number of requests/second?
@Travis - Thanks again for your hard working in maintaining TMDB and letting use these APIs <3 !
Can't find a movie or TV show? Login to create it.
Want to rate or add this item to a list?
Not a member?
Reply by vkay
on September 11, 2021 at 9:04 AM
Just as an recommendation from a developer: If you have the opportunity to implement backpressure strategies (=> reactive programming), I'd recommend to make use of it. For an example, you could add a timeout (probably 200 milliseconds) between each request instead of each keystroke, so the app would ignore/drop some "irrelevant requests".
There is no rate limiting: https://developers.themoviedb.org/3/getting-started/request-rate-limiting
Reply by eternalwolf
on September 11, 2021 at 9:06 AM
This is very helpful, will look into it.
Wow, that's crazy though. So there is no limit whatsoever to DAU/MAU limits huh... awesome.
Thanks vkay :D !
Reply by vkay
on September 11, 2021 at 10:38 AM
You're welcome ;)