Download the PHP package stechstudio/backoff without Composer
On this page you can find all versions of the php package stechstudio/backoff. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download stechstudio/backoff
More information about stechstudio/backoff
Files in stechstudio/backoff
Package backoff
Short Description PHP library providing retry functionality with multiple backoff strategies and jitter support
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package backoff
PHP Backoff
Easily wrap your code with retry functionality. This library provides:
- 4 backoff strategies (plus the ability to use your own)
- Optional jitter / randomness to spread out retries and minimize collisions
- Wait time cap
- Callbacks for custom retry logic or error handling
Installation
Defaults
This library provides sane defaults so you can hopefully just jump in for most of your use cases.
By default the backoff is quadratic with a 100ms base time (attempt^2 * 100), a max of 5 retries, and no jitter.
Quickstart
The simplest way to use Backoff is with the global backoff helper function:
If successful $result will contain the result of the closure. If max attempts are exceeded the inner exception is re-thrown.
You can of course provide other options via the helper method if needed.
Method parameters are $callback, $maxAttempts, $strategy, $waitCap, $useJitter.
Backoff class usage
The Backoff class constructor parameters are $maxAttempts, $strategy, $waitCap, $useJitter.
Or if you are injecting the Backoff class with a dependency container, you can set it up with setters after the fact. Note that setters are chainable.
Changing defaults
If you find you want different defaults, you can modify them via static class properties:
You might want to do this somewhere in your application bootstrap for example. These defaults will be used anytime you create an instance of the Backoff class or use the backoff() helper function.
Strategies
There are four built-in strategies available: constant, linear, polynomial, and exponential.
The default base time for all strategies is 100 milliseconds.
Constant
This strategy will sleep for 500 milliseconds on each retry loop.
Linear
This strategy will sleep for attempt * baseTime, providing linear backoff starting at 200 milliseconds.
Polynomial
This strategy will sleep for (attempt^degree) * baseTime, so in this case (attempt^3) * 100.
The default degree if none provided is 2, effectively quadratic time.
Exponential
This strategy will sleep for (2^attempt) * baseTime.
Specifying strategy
In our earlier code examples we specified the strategy as a string:
This would use the ConstantStrategy with defaults, effectively giving you a 100 millisecond sleep time.
You can create the strategy instance yourself in order to modify these defaults:
You can also pass in an integer as the strategy, will translates to a ConstantStrategy with the integer as the base time in milliseconds:
Finally, you can pass in a closure as the strategy if you wish. This closure should receive an integer attempt and return a sleep time in milliseconds.
Wait cap
You may want to use a fast growing backoff time (like exponential) but then also set a max wait time so that it levels out after a while.
This cap can be provided as the fourth argument to the backoff helper function, or using the setWaitCap() method on the Backoff class.
Jitter
If you have a lot of clients starting a job at the same time and encountering failures, any of the above backoff strategies could mean the workers continue to collide at each retry.
The solution for this is to add randomness. See here for a good explanation:
https://www.awsarchitectureblog.com/2015/03/backoff.html
You can enable jitter by passing true in as the fifth argument to the backoff helper function, or by using the enableJitter() method on the Backoff class.
We use the "FullJitter" approach outlined in the above article, where a random number between 0 and the sleep time provided by your selected strategy is used.
Custom retry decider
By default Backoff will retry if an exception is encountered, and if it has not yet hit max retries.
You may provide your own retry decider for more advanced use cases. Perhaps you want to retry based on time rather than number of retries, or perhaps there are scenarios where you would want retry even when an exception was not encountered.
Provide the decider as a callback, or an instance of a class with an __invoke method. Backoff will hand it four parameters: the current attempt, max attempts, the last result received, and the exception if one was encountered. Your decider needs to return true or false.
Error handler callback
You can provide a custom error handler to be notified anytime an exception occurs, even if we have yet to reach max attempts. This is a useful place to do logging for example.
