README

• ref: https://github.com/jhurliman/node-rate-limiter

Provides a generic rate limiter for the web and node.js. Useful for API clients, web crawling, or other tasks that need to be throttled. Two classes are exposed, RateLimiter and TokenBucket. TokenBucket provides a lower level interface to rate limiting with a configurable burst rate and drip rate. RateLimiter sits on top of the token bucket and adds a restriction on the maximum number of tokens that can be removed each interval to comply with common API restrictions such as "150 requests per hour maximum".

Installation

composer require wpjscc/reactphp-limiter

Usage

A simple example allowing 150 requests per hour:

use Wpjscc\React\Limiter\RateLimiter;
use function React\Async\async;
use function React\Async\await;

// Allow 150 requests per hour (the Twitter search limit). Also understands
// 'second', 'minute', 'day', or a number of milliseconds
$limiter = new RateLimiter(150, "hour");

async (function sendRequest() {
  // This call will throw if we request more than the maximum number of requests
  // that were set in the constructor
  // remainingRequests tells us how many additional requests could be sent
  // right this moment
    $remainingRequests = await($limiter->removeTokens(1));
    callMyRequestSendingFunction(...);
})();

Another example allowing one message to be sent every 250ms:

use Wpjscc\React\Limiter\RateLimiter;
use function React\Async\async;
use function React\Async\await;

$limiter = new RateLimiter(1, 250);

async(function sendMessage() {
    $remainingMessages = await($limiter->removeTokens(1));
    callMyMessageSendingFunction(...);
})();

The default behaviour is to wait for the duration of the rate limiting that's currently in effect before the promise is resolved, but if you pass in "fireImmediately": true, the promise will be resolved immediately with remainingRequests set to -1:

use Wpjscc\React\Limiter\RateLimiter;
use function React\Async\async;
use function React\Async\await;

$limiter = new RateLimiter(
    150,
    "hour",
    true
);

async(function requestHandler(request, response) {
  // Immediately send 429 header to client when rate limiting is in effect
  $remainingRequests = await($limiter->removeTokens(1));
  if ($remainingRequests < 0) {
    $response.writeHead(429, {'Content-Type': 'text/plain;charset=UTF-8'});
    $response.end('429 Too Many Requests - your IP is being rate limited');
  } else {
    callMyMessageSendingFunction(...);
  }
})();

A synchronous method, tryRemoveTokens(), is available in both RateLimiter and TokenBucket. This will return immediately with a boolean value indicating if the token removal was successful.

use Wpjscc\React\Limiter\RateLimiter;
use function React\Async\async;
use function React\Async\await;

$limiter = new RateLimiter(10,"second");

if ($limiter->tryRemoveTokens(5))
  echo('Tokens removed');
else
  echo('No tokens removed');

To get the number of remaining tokens outside the removeTokens promise, simply use the getTokensRemaining method.

use Wpjscc\React\Limiter\RateLimiter;
use function React\Async\async;
use function React\Async\await;

$limiter = new RateLimiter(1, 250);

// Prints 1 since we did not remove a token and our number of tokens per
// interval is 1
echo($limiter->getTokensRemaining());

Using the token bucket directly to throttle at the byte level:

use Wpjscc\React\Limiter\TokenBucket;
use function React\Async\async;
use function React\Async\await;

define("BURST_RATE", 1024 * 1024 * 150); // 150KB/sec burst rate
define("FILL_RATE", 1024 * 1024 * 50); // 50KB/sec sustained rate

// We could also pass a parent token bucket in to create a hierarchical token
// bucket
// bucketSize, tokensPerInterval, interval
const bucket = new TokenBucket(
  BURST_RATE,
  FILL_RATE,
  "second"
);

async(function handleData($myData) use ($bucket) {
  await($bucket->removeTokens(strlen($myData));
  sendMyData($myData);
})();

Additional Notes

Both the token bucket and rate limiter should be used with a message queue or some way of preventing multiple simultaneous calls to removeTokens(). Otherwise, earlier messages may get held up for long periods of time if more recent messages are continually draining the token bucket. This can lead to out of order messages or the appearance of "lost" messages under heavy load.

License

MIT License