From the design aspect, we like to have a backend connector that place parallel http requests to google drive platform
This platform has rate limit on the number of incoming requests per user.
Retry after
header in the http response with status code 429 will help the connector to delay in invoking next http request, but this is synchronous behavior.
Using Retry after
header, how do we achieve parallelism? By minimising number of 429 http responses that inturn improves responsiveness in front end
Is there an industry proven algorithm that can allow parallel http requests with minimum 429 response?
Aucun commentaire:
Enregistrer un commentaire