ingatlancom/php-circuit-breaker

PHP Circuit Breaker component

Maintainers

Details

github.com/ingatlancom/php-circuit-breaker

Homepage

Source

Installs: 20 325

Dependents: 0

Suggesters: 0

Security: 0

Stars: 1

Watchers: 3

Forks: 32

1.0.3 2019-02-18 14:31 UTC

Requires

  • php: >=5.3.0

Requires (Dev)

MIT 8d690ef9be9202d7a14a5e9e364e560260b62da3

error handlingcircuit breakergraceful

This package is auto-updated.

Last update: 2022-09-25 19:00:38 UTC

README

Build Status

A component helping you gracefully handle outages and timeouts of external services (usually remote, 3rd party services).

It is a library providing extremely easy to use circuit breaker component. It does not require external dependencies and it has default storage implementations for APC, Memcached or Redis but can be extended multiple ways.

Frameworks support

This library does not require any particular PHP framework, all you need is PHP 5.3 or higher.

Symfony 2

If you are using Symfony 2 framework you should use php-circuit-breaker-bundle. It is a bundle i have created to wrap up php-circuit-breaker and integrate it with Symfony 2 components and Dependency Injection.

Other Frameworks

If you are using other frameworks and you would like to use php-circuit-breaker please let me know and we can try to build up an open source integration just like the one for Symfony 2.

Motivation & Benefits

  • Allow application to detect failures and adapt its behaviour without human intervention.
  • Increase robustness of services by addinf fail-safe functionality into modules.

Installation

You can download sources and use them with your autoloader or you can use composer in which case all you nees is a require like this:

"require": {
    "ingatlancom/php-circuit-breaker": "*"
},

After that you should update composer dependencies and you are good to go.

Use Case - Non-Critical Feature

  • Your application has an Non-Critical Feature like: user tracking, stats, recommendations etc
  • The optional feature uses remote service that causes outages of your application.
  • You want to keep applicaton and core processes available when "Non-Critical Feature" fails.

Code of your application could look something like:

    $factory = new Ejsmont\CircuitBreaker\Factory();
    $circuitBreaker = $factory->getSingleApcInstance(30, 300);

    $userProfile = null;
    if( $circuitBreaker->isAvailable("UserProfileService") ){
        try{
            $userProfile = $userProfileService->loadProfileOrWhatever();
            $circuitBreaker->reportSuccess("UserProfileService");
        }catch( UserProfileServiceConnectionException $e ){
            // network failed - report it as failure
            $circuitBreaker->reportFailure("UserProfileService");
        }catch( Exception $e ){
            // something went wrong but it is not service's fault, dont report as failure
        }
    }
    if( $userProfile === null ){
        // for example, show 'System maintenance, you cant login now.' message
        // but still let people buy as logged out customers.
    }

Use Case - Payment Gateway

  • Web application depends on third party service (for example a payment gateway).
  • Web application needs to keep track when 3rd party service is unavailable.
  • Application can not become slow/unavailable, it has to tell user that features are limited or just hide them.
  • Application uses circuit breaker before checkout page rendering and if particular payment gateway is unavailable payment option is hidden from the user.

As you can see that is a very powerful concept of selectively disabling feautres at runtime but still allowing the core business processes to be uninterrupted.

Backend talking to the payment service could look like this:

    $factory = new Ejsmont\CircuitBreaker\Factory();
    $circuitBreaker = $factory->getSingleApcInstance(30, 300);

    try{
        // try to process the payment
        // then tell circuit breaker that it went well
        $circuitBreaker->reportSuccess("PaymentOptionOne");
    }catch( SomePaymentConnectionException $e ){
        // If you get network error report it as failure
        $circuitBreaker->reportFailure("PaymentOptionOne");
    }catch( Exception $e ){
        // in case of your own error handle it however it makes sense but
        // dont tell circuit breaker it was 3rd party service failure
    }

Since you are recording failed and successful operations you can now use them in the front end as well to hide payment options that are failing.

Frontend rendering the available payment options could look like this:

    $factory = new Ejsmont\CircuitBreaker\Factory();
    $circuitBreaker = $factory->getSingleApcInstance(30, 300);

    if ($circuitBreaker->isAvailable("PaymentOptionOne")) {
        // display the option
    }

Features

  • Track multiple services through a single Circuit Breaker instance.
  • Pluggable backend adapters, provided APC and Memcached by default.
  • Customisable service thresholds. You can define how many failures are necessary for service to be considered down.
  • Customisable retry timeout. You do not want to disable the service forever. After provided timeout circuit breaker will allow a single process to attempt

Performance Impact

Overhead of the Circuit Breaker is negligible.

APC implementation takes roughly 0.0002s to perform isAvailable() and then reportSuccess() or reportFailure().

Memcache adapter is in range of 0.0005s when talking to the local memcached process.

The only potential performance impact is network connection time. If you chose to use remote memcached server or implement your own custom StorageAdapter.

Running tests

Tests are run via PHPUnit. You can run all tests by any of the following:

phpunit //or vendor/bin/phpunit

You can run selected test case by running:

cd tests
phpunit Unit/Ejsmont/CircuitBreaker/Storage/Adapter/DummyAdapterTest.php

Details

Before documentation gets updated you can read more on the concept of circuit breaker and its implementation on my blog http://artur.ejsmont.org/blog/circuit-breaker

Some implementation details has changed but the core logic is still the same.

Author