Hi! At first, thank you for great async library! I tried examples and played exercises using documentation. It was full of fun!
My suggestion is providing rate control primitives (e.g. simple rate limit, smart (leaky bucket / token bucket) algorithm).
Sometimes I want rate control in production concurrent programming (e.g. batch processing along HTTP API).
Of course, we can implement simple control using par() and Source.tick(). But in production use, I think out-of-the-box rate control primitives is preferred.
Thanks! Definitely, rate control is something that will be great to include, and very much in-line with the scope of the project, in the "resiliency" part.
Hi! At first, thank you for great async library! I tried examples and played exercises using documentation. It was full of fun!
My suggestion is providing rate control primitives (e.g. simple rate limit, smart (leaky bucket / token bucket) algorithm).
Sometimes I want rate control in production concurrent programming (e.g. batch processing along HTTP API).
Of course, we can implement simple control using
par()
andSource.tick()
. But in production use, I think out-of-the-box rate control primitives is preferred.