Download the PHP package villermen/token-bucket without Composer
On this page you can find all versions of the php package villermen/token-bucket. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download villermen/token-bucket
More information about villermen/token-bucket
Files in villermen/token-bucket
Package token-bucket
Short Description Implementation of the token bucket algorithm.
License WTFPL
Homepage https://github.com/jouwweb/token-bucket
Informations about the package token-bucket
[!CAUTION] This project is archived. Please implement the more recent symfony/rate-limiter. It also implements the token bucket algorithm and enjoys better support.
Token Bucket
This is a fork of bandwidth-throttle/token-bucket originally created to add support for zend-cache (now laminas-cache).
This is a threadsafe implementation of the Token Bucket algorithm in PHP. You can use a token bucket to limit an usage rate for a resource. (E.g., a stream bandwidth or an API usage.)
The token bucket is an abstract metaphor and can be applied in throttling both consumption and production of resources. E.g., you can limit the consumption rate of a third party API, or you can limit the rate at which others can use yours.
Installation
Use Composer:
Example
This example will limit the rate of a global resource to 10 requests per second for all requests.
Note: In this example TokenBucket::bootstrap()
is part of the code.
This is not recommended for production, as this is producing unnecessary storage communication.
TokenBucket::bootstrap()
should be part of the application's bootstrap or deploy process to provide an intial amount of available tokens.
BlockingConsumer
In the example we either served the request or failed with the HTTP status 429.
This is a very resource efficient way of throttling requests, but sometimes it is desirable to not fail but instead wait untill the request can pass.
You can achieve this by consuming the token bucket with an instance of BlockingConsumer
:
Adding this to the previous example will effectively limit the rate to 10 requests per seconds all the same. However, the client does not have to handle the 429 error and instead has to sometimes wait a bit longer.