express-rate-limit
Leaky bucket strategy
Description
I am crossposting this from express-rate-limit, since it is a Store improvement suggestion.
Original post: #https://github.com/express-rate-limit/express-rate-limit/issues/359#issue-1799456039
Why
.
Alternatives
.
I left some comments on the original post. Basically I think it's fine if somebody wants to do it in their own store, but I don't really think it's worth the trouble in the official ones for a couple of reasons:
-
Leaky bucket prevents some of the optimizations that we have.
-
It was impossible to represent with the older header standards, although it might actually be possible with the latest draft.
If we did do it officially, I think I would want to do a redesign of the whole project so that the strategy and store were independent of eachother, and every strategy could work with every store. But that seems like a ton of work, and probably not worth the effort.
