The Search API endpoint is rate limited based on Client ID rather than what user is making the request, so all simultaneous users will be subject to the same rate limit.
From docs it's not clear at what point the app would be rate limited; the only thing I could do is wait out rate limit errors instead of returning error to user.
"If Web API returns status code 429, it means that you have sent too many requests. When this happens, check the Retry-After header, where you will see a number displayed. This is the number of seconds that you need to wait, before you try your request again."
This seems like a potentially big scaling problem.
The Search API endpoint is rate limited based on Client ID rather than what user is making the request, so all simultaneous users will be subject to the same rate limit.
From docs it's not clear at what point the app would be rate limited; the only thing I could do is wait out rate limit errors instead of returning error to user.
"If Web API returns status code 429, it means that you have sent too many requests. When this happens, check the Retry-After header, where you will see a number displayed. This is the number of seconds that you need to wait, before you try your request again."
This seems like a potentially big scaling problem.