For the latest stable version, please use Spring-Cloud-CircuitBreaker 3.3.0!spring-doc.cn

Bulkhead pattern supporting

If resilience4j-bulkhead is on the classpath, Spring Cloud CircuitBreaker will wrap all methods with a Resilience4j Bulkhead. You can disable the Resilience4j Bulkhead by setting spring.cloud.circuitbreaker.bulkhead.resilience4j.enabled to false.spring-doc.cn

Spring Cloud CircuitBreaker Resilience4j provides two implementation of bulkhead pattern:spring-doc.cn

  • a SemaphoreBulkhead which uses Semaphoresspring-doc.cn

  • a FixedThreadPoolBulkhead which uses a bounded queue and a fixed thread pool.spring-doc.cn

By default, Spring Cloud CircuitBreaker Resilience4j uses FixedThreadPoolBulkhead. To modify the default behavior to use SemaphoreBulkhead set the property spring.cloud.circuitbreaker.resilience4j.enableSemaphoreDefaultBulkhead to true.spring-doc.cn

For more information on implementation of Bulkhead patterns see the Resilience4j Bulkhead.spring-doc.cn

The Customizer<Resilience4jBulkheadProvider> can be used to provide a default Bulkhead and ThreadPoolBulkhead configuration.spring-doc.cn

@Bean
public Customizer<Resilience4jBulkheadProvider> defaultBulkheadCustomizer() {
    return provider -> provider.configureDefault(id -> new Resilience4jBulkheadConfigurationBuilder()
        .bulkheadConfig(BulkheadConfig.custom().maxConcurrentCalls(4).build())
        .threadPoolBulkheadConfig(ThreadPoolBulkheadConfig.custom().coreThreadPoolSize(1).maxThreadPoolSize(1).build())
        .build()
);
}