3 ms·
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 pe
by nebiyu 10y ago
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 https://github.com/jhalterman/failsafe#retries
- Hydraulix989 10y agoWhat do you recommend for JS?
- nebiyu 10y agoLibraries that provide similar abstractions in js do exist (https://github.com/tim-kos/node-retry https://github.com/tim-kos/node-retry and https://github.com/MathieuTurcotte/node-backoff https://github.com/MathieuTurcotte/node-backoff), but I'm not qualified to recommend anything. Most of the colleagues I've had have rolled their own one off solutions when needed.