Download the PHP package tleckie/circuit-breaker without Composer
On this page you can find all versions of the php package tleckie/circuit-breaker. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download tleckie/circuit-breaker
More information about tleckie/circuit-breaker
Files in tleckie/circuit-breaker
Package circuit-breaker
Short Description With the powerful Circuit Breaker library in PHP you will be able to manage and protect your application from requests that stop working to avoid overloads. The implementation that you will have to do is very simple.
License MIT
Homepage https://github.com/teodoroleckie/circuit-breaker
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 circuit-breaker
PHP Circuit Breaker
With the powerful Circuit Breaker library you will be able to manage and protect your application from requests that stop working to avoid overloads. The implementation that you will have to do is very simple.
Installation:
You can install the package via composer:
It's common for software systems to make remote calls to software running in different processes, probably on different machines across a network. One of the big differences between in-memory calls and remote calls is that remote calls can fail, or hang without a response until some timeout limit is reached. What's worse if you have many callers on a unresponsive supplier, then you can run out of critical resources leading to cascading failures across multiple systems. In his excellent book Release It, Michael Nygard popularized the Circuit Breaker pattern to prevent this kind of catastrophic cascade.
The basic idea behind the circuit breaker is very simple. You wrap a protected function call in a circuit breaker object, which monitors for failures. Once the failures reach a certain threshold, the circuit breaker trips, and all further calls to the circuit breaker return with an error, without the protected call being made at all. Usually you'll also want some kind of monitor alert if the circuit breaker trips.
Circuit breaker is heavily used in microservice architecture to find issues between microservices calls. The main idea is to protect your code from making unnecessary calls if the microservice you call is down.
Features:
- Automatic update. (i.e you don't have to manually add success or failure method like other library)
- Return result from the protected function.
- Retry timeout.
- Protect your services calls if they are dropped.
Usage:
- You have to create an instance of the CircuitBreaker class with three arguments. The first must be an instance of your preferred psr-16 cache, it must implement the Psr\SimpleCache\CacheInterface interface and is not included with this library.
- The second required argument is the number of retries the library must do before entering the open state.
- The third argument is the time in seconds that the circuit must wait before making new calls to the protected service.
- The CircuitBreaker class makes available the callService method in which a closure must be implemented to call the service from within.
- Within the closure, the exception that would be fired when the service is not operational must be controlled, said exception is caught and a CircuitBreakerException exception is created, passing through its constructor the one that has been handled.
- At this point, the service is fully protected against failure.
- When CircuitBreaker goes to the open state, that is, the service is not functional, it will stop receiving requests by throwing the last known exception in all cases until the service is available to receive new requests.
- The whole process is transparent and automatic for you.
- Given the nature of the microservices' architecture, it is recommended to use a centralized cache storage shared between all your frontend and backend machines.
