Resilience4j: TimeLimiter as rx operator

[edudar]

Timeouts and time limiters are essential for resiliency and one of the primary reasons we use Hystrix in the first place. TimeLimiterOperators are really missing in -rxjava2 and -reactor packages.

[RobWin]

Hi,

the RxJava and Reactor timeout operator is not sufficient for you?

http://reactivex.io/documentation/operators/timeout.html and https://projectreactor.io/docs/core/release/api/reactor/core/publisher/Flux.html#timeout-java.time.Duration-

[edudar]

I can't say whether it's sufficient as a whole or not but I can make it work in some cases for sure. Same as I can make it with debounce and retry, for example, yet there are convenient operators for them wired into the whole resilience system. With only time limiter missing there, it feels inconsistent but if that's a design decision, fine.

[storozhukBM]

It seems to me that Hystrix is achieving such time limiting capabilities by running all protected command inside separate thread pool.
Yes, according to our design we don't want to enforce such execution model for our users. But possibly we can implement similar solution and make it optional.
Take a look at #146