With DataStoreService, there’s a Get/SetAsync limit of 60 + numPlayers * 10
HttpService doesn’t match the consistency of DataStoreService’s limits, which is a linear relationship.
I don’t see why HttpService is capped to 500 per server, regardless if there is 1 player in the server or 200 players. In cases like backing up user data to an external website, you would either have a ton of leftover requests or barely struggling to keep up under the limit.
Perhaps the cap for HttpService could be the same as DataStoreService.
1 Like
What would require more than 500 a minute? Any specific use cases?
2 Likes
I don’t know, but it sure isn’t with consistency with DataStoreService’s limit.
They may be willing to raise the limit if there are enough strong use cases, but you or someone else has to specify these.
What you mention doesn’t seem very convincing for increasing the limit, because suppose you only save data for each player once every minute (which is already quite frequent), that would only consume 200 requests at most in a 200 player server (which you would probably not even reach, since 200 players on a base plate already seems too much for Roblox to handle right now).
1 Like
We’ve talked about doing this but usually when a developer is sending more than 500 requests per minute, they are trying to do something involving realtime communication like cross server chat. There are better ways to support these use cases than with HTTP requests.
2 Likes