spring-cloud / spring-cloud/spring-cloud-circuitbreaker
Expose underlying Circuit Breaker implementation instance to allow for additional configuration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 355
- Forks
- 123
- Avg merge
- 5h 25m
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe.
While it certainly is a perfectly defensible position that SCCB (as per its name) should only support the "CircuitBreaker" pattern - it may be more robust to allow for configuration of additional library-specific resilience patterns. For instance Resilience4j enables 7 different resilience patterns of which only CircuitBreaker and TimeLimiter are supported
Describe the solution you'd like
Would love to have a mechanism to more fully configure the underlying circuit breaker's implementation, for instance to also enable Retry.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with spring-cloud-circuitbreaker-resilience4j/src/main/java/org/springframework/cloud/circuitbreaker/resilience4j/Resilience4JConfigBuilder.java and review how CircuitBreaker and TimeLimiter are configured. Compare the supported configuration with the Resilience4j resilience patterns linked in the issue; done means a documented mechanism exists to configure an additional pattern such as Retry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100