circuit_breaker alternatives and similar shards
Based on the "Misc" category.
Alternatively, view circuit_breaker alternatives based on common mentions on social networks and blogs.
Do you think we are missing an alternative of circuit_breaker or a related project?
Simple Implementation of the circuit breaker pattern in Crystal.
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. - Martin Fowler
Given a certain error threshold, timeframe and timeout window, a breaker can be used to monitor criticial command executions. Circuit breakers are usually used to prevent unnecessary requests if a server ressource et al becomes unavailable. This protects the server from additional load and allows it to recover and relieves the client from requests that are doomed to fail.
Wrap API calls inside a breaker, if the error rate in a given time frame surpasses a certain threshold, all subsequent calls will fail for a given duration.
Add to your shard.yml
dependencies: circuit_breaker: github: tpei/circuit_breaker branch: master
and then install the library into your project with
$ crystal deps
Create a new breaker:
require "circuit_breaker" breaker = CircuitBreaker.new( threshold: 5, # % of errors before you want to trip the circuit timewindow: 60, # in s: anything older will be ignored in error_rate reenable_after: 300 # after x seconds, the breaker will allow executions again )
Then wrap whatever you like:
breaker.run do my_rest_call() end
Handling CircuitBreaker trips
The Breaker will open and throw an CircuitOpenException for all subsequent calls, once the threshold is reached. You can of course catch these exceptions and do whatever you want :D
begin breaker.run do my_rest_call() end rescue exc : CircuitOpenException log "happens to the best of us..." 42 end
After the given reenable time, the circuit will transition to "half open". This will completely reset the circuit if the next execution succeeds, but reopen the circuit and reset the timer if the next execution fails.
Handling only certain error types
If you are feeling really funky, you can also limit the exception classes to monitor. You might want to catch
RandomRestError, but not
ArgumentError, so do this:
breaker = CircuitBreaker.new( threshold: 5, timewindow: 60, reenable_after: 300, handled_errors: [RandomRestError.new] ) breaker.run raise ArgumentError.new("won't count towards the error rate") end
Ignoring certain error types
Conversely, you can also add custom errors to ignore and count all others:
breaker = CircuitBreaker.new( threshold: 5, timewindow: 60, reenable_after: 300, ignored_errors: [ArgumentError.new] ) breaker.run raise ArgumentError.new("won't count towards the error rate") end
Unfortunately this both won't match against exception subclasses just yet, so at the moment you have to specify the exact class to monitor and can't just use
RestException to match every subclass like
RestTimeoutException < RestException...
Special thanks goes to Pedro Belo on whose ruby circuit breaker implementation (CB2) this is loosely based.