Please select
  • Projects 5
  • Rating 4.9
  • Rating 756

Budget: 700 UAH Deadline: 7 days

Hello, I recently worked on a similar high-load request sender: a connection pool, asynchronous workers, batching, and rate limit control for 100-200k requests per minute. Retries with backoff and a queue for failed requests were part of the same solution.

If requests are going to an external API with limits, it's worth implementing a queue and adaptive throttle right away, as this saves from bans and data loss under peak load.

Where exactly are the requests being sent - to your own server or an external API, and does it have a limit on the number of requests per minute? And where is this supposed to run - a one-time launch or a continuous service?

I suggest we get in touch; I can also sketch out a solution diagram with a queue and workers for your 200k per minute.

  • Projects 11
  • Rating 5.0
  • Rating 914

Budget: 2500 UAH Deadline: 2 days

Hello! I can do it urgently.

Please clarify which URL to send the GET requests to, whether unique parameters are needed or just identical requests, from which server the requests will be initiated, and if 100-200 thousand requests per minute are required from one server or if distributed sending is allowed.

  • Projects 6
  • Rating 3.9
  • Rating 776

Budget: 700 UAH Deadline: 2 days

Anton, the task is to ensure high throughput for GET requests, where the main challenge is not the request code itself, but the effective operation with the network stack and avoiding server-side blocking under such load. For stable operation of 200k requests per minute, it is necessary to use asynchronous threads and connection optimization to avoid wasting resources on establishing new sessions. How do you plan to handle responses from the server at such intensity, do they need to be stored somewhere or analyzed in real-time?