rate

Choosing the optimal number of buckets requires understanding collision probabilities and load factors from the advanced usage section, which can be non-trivial and error-prone for developers.

Lacks out-of-the-box HTTP middleware or framework support, requiring manual integration for common use cases like API rate limiting, as it focuses on core algorithms only.

The RotatingTokenBucketLimiter uses twice the memory and token consumption for collision resistance, with a performance overhead of ~2x compared to the standard token bucket, as noted in its trade-offs.

Designed for in-memory rate limiting on a single server, with no native support for distributed rate limiting across multiple instances, limiting its use in scaled-out architectures.