Skip to content
Modules

Resilience

Execution Resilience

failover-execution-resilience wraps upstream calls in a Resilience4j circuit-breaker, providing fast-fail behaviour when an upstream service is repeatedly failing.

Dependency

<dependency>
    <groupId>com.societegenerale.failover</groupId>
    <artifactId>failover-execution-resilience</artifactId>
    <version>3.0.0</version>
</dependency>

Also requires Spring Cloud Circuit Breaker on the classpath:

<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-circuitbreaker-resilience4j</artifactId>
</dependency>

Enable

application.yml
failover:
  type: resilience

With type: resilience, FailoverAspect uses ResilienceFailoverExecution instead of BasicFailoverExecution. The circuit-breaker wraps the upstream call before the try/catch handoff to FailoverHandler.

Circuit Breaker Behaviour

stateDiagram-v2
    direction LR
    Closed --> Open : failure threshold exceeded
    Open --> HalfOpen : wait duration elapsed
    HalfOpen --> Closed : probe call succeeds
    HalfOpen --> Open : probe call fails
    Open --> [*] : CallNotPermittedException → triggers recovery immediately

When the circuit is Open, the upstream call is not attempted. CallNotPermittedException is thrown immediately and FailoverHandler.recover is called — serving the last stored result without hitting the upstream at all.

Resilience4j Configuration

Configure circuit-breaker properties via Spring Cloud's standard configuration:

application.yml
resilience4j:
  circuitbreaker:
    instances:
      failover:                               # instance name used by the module
        slidingWindowSize: 10
        failureRateThreshold: 50
        waitDurationInOpenState: 30s
        permittedNumberOfCallsInHalfOpenState: 3

The default instance name is failover. Override by declaring a custom CircuitBreakerRegistry bean.

Next Steps