{"id":134692,"date":"2025-06-12T08:48:00","date_gmt":"2025-06-12T05:48:00","guid":{"rendered":"https:\/\/www.javacodegeeks.com\/?p=134692"},"modified":"2025-06-08T14:45:44","modified_gmt":"2025-06-08T11:45:44","slug":"resilience4j-circuit-breakers-in-spring-boot-3","status":"publish","type":"post","link":"https:\/\/www.javacodegeeks.com\/2025\/06\/resilience4j-circuit-breakers-in-spring-boot-3.html","title":{"rendered":"Resilience4j Circuit Breakers in Spring Boot 3"},"content":{"rendered":"

Modern microservices demand resilience: when dependencies fail or overload, you must prevent cascading failures. Resilience4j<\/strong> offers modular support for key patterns\u2014Circuit Breaker, Retry, Rate Limiter, Bulkhead\u2014all designed to empower Spring Boot 3 apps with fault tolerance without bringing in heavyweight dependencies like Hystrix.<\/p>\n

Setup for Spring Boot 3<\/h2>\n

Add these to your pom.xml<\/code>:<\/p>\n

\n<dependency>\n  <groupId>io.github.resilience4j<\/groupId>\n  <artifactId>resilience4j-spring-boot3<\/artifactId>\n<\/dependency>\n<dependency>\n  <groupId>org.springframework.boot<\/groupId>\n  <artifactId>spring-boot-starter-actuator<\/artifactId>\n<\/dependency>\n<dependency>\n  <groupId>io.github.resilience4j<\/groupId>\n  <artifactId>resilience4j-micrometer<\/artifactId>\n<\/dependency>\n<\/pre>\n
Metrics are enabled automatically via Actuator and Micrometer.<\/p>\n
Patterns: Usage Examples<\/h2>\n
1. Circuit Breaker + Retry<\/h3>\n
application.yml<\/code>:<\/strong><\/p>\n
\nresilience4j:\n  circuitbreaker:\n    configs:\n      default:\n        failureRateThreshold: 50\n        slidingWindowSize: 10\n        waitDurationInOpenState: 10s\n    instances:\n      backendService: {}\n  retry:\n    instances:\n      backendService:\n        maxAttempts: 3\n        waitDuration: 1s\n        exponentialBackoffMultiplier: 2.0\n<\/pre>\n
Service code:<\/strong><\/p>\n
\n@CircuitBreaker(name=\"backendService\", fallbackMethod=\"cbFallback\")\n@Retry(name=\"backendService\")\npublic String fetchData() {\n    return externalClient.getData();\n}\npublic String cbFallback(Throwable ex) {\n    return \"Service temporarily unavailable\";\n}\n<\/pre>\n
his retries with exponential backoff and prevents cascading failures.<\/p>\n
2. Rate Limiter<\/h3>\n
application.yml<\/code>:<\/strong><\/p>\n
\nresilience4j.ratelimiter:\n  instances:\n    apiLimiter:\n      limitForPeriod: 5\n      limitRefreshPeriod: 10s\n      timeoutDuration: 500ms\n<\/pre>\n
Controller:<\/strong>
 
<\/div> <\/div><\/p>\n
\n@RateLimiter(name=\"apiLimiter\", fallbackMethod=\"rateLimitFallback\")\n@GetMapping(\"\/limited\")\npublic String limited() {\n    return myService.callExternal();\n}\npublic String rateLimitFallback(Throwable ex) {\n    return \"Too many requests, try later.\";\n}\n<\/pre>\n
This ensures no more than 5 calls are allowed per 10 seconds.<\/p>\n
3. Bulkhead<\/h3>\n
application.yml<\/code>:<\/strong><\/p>\n
\nresilience4j.bulkhead:\n  instances:\n    bulkheadApi:\n      maxConcurrentCalls: 3\n      maxWaitDuration: 1ms\n<\/pre>\n
Endpoint:<\/strong><\/p>\n
\n@GetMapping(\"\/bulkhead\")\n@Bulkhead(name=\"bulkheadApi\", type=Bulkhead.Type.SEMAPHORE)\npublic String bulkheadCall() {\n    return externalClient.call();\n}\n@ExceptionHandler(BulkheadFullException.class)\n@ResponseStatus(HttpStatus.TOO_MANY_REQUESTS)\npublic void handleBulkhead() {}\n<\/pre>\n
This limits concurrent calls and rejects excess ones, preventing overload.<\/p>\n
Best Practices<\/h2>\n
\n\n\n\n\n\n\n\n\n\n\n\n
Pattern<\/th>\nPractice<\/th>\n<\/tr>\n<\/thead>\n
Circuit Breaker<\/strong><\/td>\nSet failure thresholds and half-open policies; centralize configs.<\/td>\n<\/tr>\n
Retry<\/strong><\/td>\nUse bounded, exponential backoff. Avoid retries without CB.<\/td>\n<\/tr>\n
Rate Limiter<\/strong><\/td>\nControl client or third-party calls to prevent resource exhaustion.<\/td>\n<\/tr>\n
Bulkhead<\/strong><\/td>\nIsolate resource pools using semaphores or threads.<\/td>\n<\/tr>\n
Metrics<\/strong><\/td>\nMonitor all patterns via Micrometer\/Actuator dashboards.<\/td>\n<\/tr>\n
Fallbacks<\/strong><\/td>\nProvide meaningful fallback responses for each pattern.<\/td>\n<\/tr>\n
Combine Wisely<\/strong><\/td>\nApply in layers: rate limiter \u2192 bulkhead \u2192 circuit breaker \u2192 retry.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n
Developer Insights<\/h2>\n
From r\/java:<\/p>\n
\n
\u201cRetries should never ever<\/em> be used in microservice landscapes between services without circuit breakers<\/strong>\u2026 retries alone will DDoS itself\u201d <\/p>\n<\/blockquote>\n
From r\/java:<\/p>\n
\n
\u201cResilience4j is pretty nice with OpenFeign\u2026 we use Bucket4J for rate limiting\u201d <\/p>\n<\/blockquote>\n
From r\/SpringBoot:<\/p>\n
\n
\u201cResilience4j is a more flexible option with retry, circuit breakers, and bulkhead patterns.\u201d <\/p>\n<\/blockquote>\n
These voices highlight that patterns must be combined smartly to avoid unintended failures.<\/p>\n
Real-World Service Integration<\/h2>\n
Compose decorators with Resilience4j\u2019s fluent API:<\/p>\n
\nSupplier<String> supplier = () -> client.call();\n\nSupplier<String> decorated = Decorators.ofSupplier(supplier)\n  .withCircuitBreaker(CircuitBreaker.ofDefaults(\"svc\"))\n  .withRateLimiter(RateLimiter.ofDefaults(\"svc\"))\n  .withBulkhead(Bulkhead.ofDefaults(\"svc\"))\n  .withRetry(Retry.ofDefaults(\"svc\"))\n  .decorate();\n\nTry.ofSupplier(decorated)\n   .recover(Throwable.class, \"fallback\");\n<\/pre>\n
This provides layered protection: rate limiting, concurrency control, circuit breaker, and retries\u2014all in one cohesive pipeline.<\/p>\n
Further Resources<\/h2>\n