Controlling Concurrency of HTTP Requests in Phoenix API

61
clicks
Controlling Concurrency of HTTP Requests in Phoenix API
In this discussion, skwyckl describes an issue where a client sends a large number of requests concurrently to their Phoenix API, causing errors due to overwhelmed Ecto connections. The author is seeking a solution to convert the massive simultaneous requests into sequential ones, similar to the behavior of another client that sends requests slightly offset without causing problems. Comments include suggestions for rate-limiting methods and the use of the Hammer library to manage request flow without affecting other clients.

© HashMerge 2024