3 ms·
> Or: I could use Spring-Retry[0]. The idea that you would add a dependency to avoid writing a try-catch in a loop is absolutely bewildering to me. What next,
by twic 10y ago
> Or: I could use Spring-Retry[0].
The idea that you would add a dependency to avoid writing a try-catch in a loop is absolutely bewildering to me. What next, Spring Pad? I can see it now:
@LeftPad(width = 50)
public String getNameForDisplay() {
return name;
}
- nimish 10y agoBeing able to quickly change in different retry mechanisms and policies is pretty useful. Sometimes you want exponential backoff, sometimes no backoff, sometimes it depends on other state. Not as simple as you might think. And if you're gonna be writing microservices you're going to be intimately familiar with retries.
- wsargent 10y agoI really like jhalterman's failsafe library. Exponential backoff, jitter, circuit breaker support, etc. https://github.com/jhalterman/failsafe https://github.com/jhalterman/failsafe
- jacques_chester 10y ago> The idea that you would add a dependency to avoid writing a try-catch in a loop is absolutely bewildering to me. Reliable retry is very important in some cases, and it's easier to test a retry-agnostic unit of code. Edit: and I also rather like that it's declarative, rather than needing to infer intention or write my own boilerplate to explicate intention.
- springsux 10y agoDeath by a thousand annotations, which used to be death by a thousand XML files.