This commit is contained in:
2020-01-10 00:04:23 +00:00
parent 83b2f042b3
commit b6e904509c

View File

@@ -37,9 +37,15 @@ TODO: DO I NOT HAVE AN ERASE DB ROUTE?
- wouldn't that make the below possible??
TODO: API RATE LIMITING / THROTTLING
- Return code 429
- Going to need rate limiting to save people from themselves
- All the big api's have hourly limits on requests and also limits on total data throughput per hour
- (minute as well which actually makes more sense since it means they would only be down for a minute if they exceed it) too
- Find out what others do
- Twitter: https://developer.twitter.com/en/docs/basics/rate-limiting
- Zendesk = 100 requests per minute max
- https://developer.yammer.com/docs/rest-api-rate-limits
- Good developer info here: https://medium.com/clover-platform-blog/conquering-api-rate-limiting-dcac5552714d
- Would be nice to have a switch to set for if we host as maximum rates they pay for maybe
- On the other hand it's likely a can of worms and maybe it's best they pay for their own hosting and we just set it up or something?
- but then it's going to be hard to self serve them where it's all done easy peasy unless we host