Spring Boot - Advanced Patterns
You want to design a Spring Boot microservice that calls an unstable external payment API. Using Resilience4j circuit breaker, which approach best ensures system stability and graceful degradation?
You want to design a Spring Boot microservice that calls an unstable external payment API. Using Resilience4j circuit breaker, which approach best ensures system stability and graceful degradation?
hard📝 Application Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Understand system stability needs
Using a circuit breaker prevents repeated calls to the unstable API, avoiding overload.Step 2: Importance of fallback for graceful degradation
A fallback method returning cached or default data keeps the system responsive during failures.Step 3: Evaluate other options
Retries alone can worsen overload; no fallback causes failures; increasing threads doesn't solve API instability.Final Answer:
Apply @CircuitBreaker with a fallback method returning a cached payment status -> Option AQuick Check:
Circuit breaker + fallback = stability + graceful degradation [OK]
Quick Trick: Combine circuit breaker with fallback for best resilience [OK]
Common Mistakes:
- Relying only on retries without circuit breaker
- Not providing fallback causing failures
- Increasing threads without handling failures
Master "Advanced Patterns" in Spring Boot
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Spring Boot Quizzes