Generator-jhipster: Using resilience4j as a possible circuit breaker option beside Hystrix

Created on 8 Apr 2019 · 7Comments · Source: jhipster/generator-jhipster

Overview of the feature request

Can we add a support to use resilience4j as a circuit breaker as an alternative to Hystrix as a Hystrix now is just on maintenance state

Motivation for or Use Case

As Hsyrix is on maintencane state and Netflix guys are pushing people to look for other alternative like Resilience4j , it would be cool to add support to it

I can help here if you would like as i am contributor in resilience4j as well.

wont-fix

Source

Romeh

All 7 comments

Sorry given the workload and options we have, I don't think we have the bandwidth to provide more options here.

deepu105 on 8 Apr 2019

Yes, it should probably replace Hystrix at some point, but I'd rather wait 1 or 2 years to see where this is going.

jdubois on 8 Apr 2019

I think we should add this to our v7 roadmap at #10958

@Romeh would you still be interested in helping on this? Do you think this is a big change (I don't expect it is, but I have no experience in this migration)?

jdubois on 26 Dec 2019

👍1

Maybe @robwin can help here too, if interested.

atomfrede on 26 Dec 2019

👍1

Is it more than "just" using spring-cloud-starter-circuitbreaker-resilience4j and adjusting application properties?

gmarziou on 26 Dec 2019

👍1

You can either use spring-cloud-circuitbreaker or our Spring Boot starter which adds much more features like support for Annotations, Spring Cloud Config support, Retry, RateLimiter, Bulkhead,...