failsafe

I really like jhalterman's failsafe library. Exponential backoff, jitter, circuit breaker support, etc. https://github.com/jhalterman/failsafe

That list of questions is why I prefer retry and back-off to be separate from the internals of the http library. As a library user I need to work around the peculiarities of the particular service endpoints I'm integrating with. Backoff and retry aren't specific to the application/transport protocol through which a service is consumed. For example, (in the java world) the approach in libraries like hysterix, guava-retrying, and failsafe https://github.com/jhalterman/failsafe#retries

Good example of where random retry delays would be valuable. I filed this as a feature to add for the next release: https://github.com/jhalterman/failsafe/issues/39

> Is there a more detailed comparison? There's nothing more detailed that I know of. Is there a particular feature area/comparison you're curious about? I can add a bit more detail. > It's not apparent to me what the advantage of either interface is. In both situations I have to define a "lambda" What I meant by this bit is that the user experience is different. Failsafe can be used with method references or lambda expressions [1], which are a nice, concise way of wrapping executable logic with some failure handling strategy. You cannot do this with Hystrix since all logic must be wrapped in a HystrixCommand impl, which cannot be implemented as a lambda. > either seems acceptable. Like anything, it just depends on what you want. If retries and general purpose failure handling, consider Failsafe. If request collapsing, thread pool manageme

Good question. Someone asked that recently on Github - here's a quick comparison: https://github.com/jhalterman/failsafe/wiki/Comparisons#fail...