Improvements

[Ladicek]

Motivation:

The context is https://github.com/vert-x3/issues/issues/633, and this commit is a first step towards that goal. It does:

• remove all the Hystrix stuff, because Hystrix is long dead
• improve documentation and implementation
• update test-scoped dependencies

I have also started working on a Resilience4j howto, which shall be linked from the documentation here. In fact, I already have Vert.x wrappers for all Resilience4j fault tolerance patterns (bulkhead, circuit breaker, rate limiter, retry, time limiter -- I didn't include cache for obvious reasons), so we could possibly make into a full-fledged extension (and deprecate the Vert.x circuit breaker maybe?). That's for later, for sure.

Conformance:

Your commits should be signed and you should have signed the Eclipse Contributor Agreement as explained in https://github.com/eclipse/vert.x/blob/master/CONTRIBUTING.md Please also make sure you adhere to the code style guidelines: https://github.com/vert-x3/wiki/wiki/Vert.x-code-style-guidelines

[Ladicek]

Added one more commit that mentions Resilience4j at the end of the documentation (where Hystrix usage used to be documented). The documentation is very brief, it mostly just points to the recently published how-to: https://how-to.vertx.io/resilience4j-howto/

[tsegismont]

I have also started working on a Resilience4j howto, which shall be linked from the documentation here. In fact, I already have Vert.x wrappers for all Resilience4j fault tolerance patterns (bulkhead, circuit breaker, rate limiter, retry, time limiter -- I didn't include cache for obvious reasons), so we could possibly make into a full-fledged extension (and deprecate the Vert.x circuit breaker maybe?). That's for later, for sure.

Another option would be a Reactiverse project for Resilience4j integration

[Ladicek]

That would make sense too, good point!

[vietj]

can you rebase this PR please @Ladicek ?

[Ladicek]

Rebased.

[vietj]

Thanks @Ladicek