@eternalwolf said: 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.

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".

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?

There is no rate limiting: https://developers.themoviedb.org/3/getting-started/request-rate-limiting

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".

This is very helpful, will look into it.

There is no rate limiting: https://developers.themoviedb.org/3/getting-started/request-rate-limiting

Wow, that's crazy though. So there is no limit whatsoever to DAU/MAU limits huh... awesome.

Thanks vkay :D !

You're welcome ;)