-
### Background and motivation
Rate limiters in the `System.Threading.RateLimiting` namespace is not designed to accept `TimeProvider`.
Therefore, we need to wait for the actual time to elapse when…
-
With the migration of the pulsar driver to the nb5 adapter API, we decided to move the per-thread rate limiter which was in the previous pulsar driver into the nb5 core, so it can be implemented more …
-
**Description:**
The Rate Limiting design pattern is crucial in a microservices architecture to prevent abuse and ensure fair usage of resources. This pattern restricts the number of requests a servic…
-
**EN**
According to the DEV documentation ([https://developer.shopware.com/docs/guides/hosting/infrastructure/rate-limiter.html?_gl=1*5h7k4n*_ga*MTkyODE0ODE0OS4xNzA2MDc5MTkx*_ga_9JLJ6GGB76*MTcwNzgw…
-
What do you think about implementing a default balancer to avoid flood limits requests api?
For example all Raw calls are queued and make sure that only 30 req/s can be done
-
### Proposal Details
Currently, `golang.org/x/time/rate.Limiter` allows setting limit and burst, but not available buckets.
I am interested in the use case where I use `Limiter` to limit my own ca…
mitar updated
1 month ago
-
### Proposal Details
### Proposal Details
Currently, `golang.org/x/time/rate.Limiter` provides handy `Wait` and `WaitN` methods. But when using them, it is not really possible to know later on if …
mitar updated
1 month ago
-
Hi !
Working on the argopy documentation (that was taking an unusual long time to build), I noticed that the last argovis API looks much slower than the previous one...
If you compare numbers us…
-
### Background and motivation
It would be nice to be able to AND (and possibly OR) rate limiters together.
For example, "I want a rate limiter that allows no more than 10 requests per second and…
-
*Title*: *need help passing metadata to async gRPC request*
*Description*:
I have a use case where an async Rate-Limit unary gRPC request is created,
To issue the request, we use:
`async_clien…