bentools / guzzle-throttle-middleware
A GuzzleHTTP Middleware that can delay requests before sending them.
Installs: 247 421
Dependents: 1
Suggesters: 0
Security: 0
Stars: 15
Watchers: 3
Forks: 9
Open Issues: 1
Requires
- php: >=7.0
- bentools/psr7-request-matcher: ^1.0
- guzzlehttp/guzzle: ^6.0
- psr/log: ^1.0
Requires (Dev)
- bentools/guzzle-duration-middleware: ^1.0
- phpunit/phpunit: @stable
- psr/cache: ^1.0
- satooshi/php-coveralls: @stable
- squizlabs/php_codesniffer: @stable
- symfony/cache: ^3.3
- symfony/var-dumper: ^3.3
README
Guzzle Throttle Middleware
This middleware adds throttling capabilities to your Guzzle client.
This can be useful when some hosts limits your number of requests per second / per minute.
Installation
composer require bentools/guzzle-throttle-middleware
Counter storage
By default, request counters are stored in an array.
But you can use the PSR6Adapter
to store your counters within a psr/cache implementation,
such as symfony/cache, and use shared storages like Redis, APCu, Memcached, ...
Usage
For this middleware to work, you need to register some configurations.
A configuration is composed of:
- A Request matcher (to trigger or not the throttler, depending on the request content)
- A maximum number of requests
- The period, in seconds, during which the maximum number of requests apply.
- A storage key.
You can register as many configurations as you need. The 1st request matcher wins.
Example
namespace App\RequestMatcher; use BenTools\Psr7\RequestMatcherInterface; use Psr\Http\Message\RequestInterface; class ExampleOrgRequestMatcher implements RequestMatcherInterface { /** * @inheritDoc */ public function matchRequest(RequestInterface $request) { return false !== strpos($request->getUri()->getHost(), 'example.org'); } }
use App\RequestMatcher\ExampleOrgRequestMatcher; use BenTools\GuzzleHttp\Middleware\Storage\Adapter\ArrayAdapter; use BenTools\GuzzleHttp\Middleware\ThrottleConfiguration; use BenTools\GuzzleHttp\Middleware\ThrottleMiddleware; use GuzzleHttp\Client; use GuzzleHttp\HandlerStack; require_once __DIR__ . '/vendor/autoload.php'; $stack = HandlerStack::create(); $middleware = new ThrottleMiddleware(new ArrayAdapter()); // Max 1 request per second $maxRequests = 1; $durationInSeconds = 1; $middleware->registerConfiguration( new ThrottleConfiguration(new ExampleOrgRequestMatcher(), $maxRequests, $durationInSeconds, 'example') ); $stack->push($middleware, 'throttle'); $client = new Client([ 'handler' => $stack, ]); $client->get('http://www.example.org'); // Will be executed immediately $client->get('http://www.example.org'); // Will be executed in 1 second
Tests
./vendor/bin/phpunit
Known issues
Due to PHP's synchronous behaviour, remember that throttling means calling sleep()
or usleep()
functions, which will delay your entire script, and not only the current request.
This means throttling will also block Guzzle's asynchronous requests when using CurlMultiHandler
.
To prevent this, you may have a look at bentools/guzzle-queue-handler, a handler that delegates asynchronous requests to PHP workers (Beanstalk, RabbitMQ, Redis, ...).
You can then enable throttling only on workers.
See also
- bentools/guzzle-queue-handler - A queue handler to process Guzzle 6+ requests within a work queue.
- kevinrob/guzzle-cache-middleware - A HTTP Cache for Guzzle 6. It's a simple Middleware to be added in the HandlerStack.
- bentools/guzzle-duration-middleware - A Guzzle 6+ Middleware that adds a X-Request-Duration header to all responses to monitor response times.