sttp
sttp copied to clipboard
RetryBackend based on softwaremill/retry
While porting an application to Tapir, I ended up writing an integration between sttp and retry.
Since both libraries are part of softwaremill, it would be nice to have such integration built in.
Here I used Backoff, but it could receive a retry policy and be more generic.
Would something like this make sense?
One problem I see is that retry is still in 0.x phase, so maybe the integration can have 03 in the package name to avoid breaking changes?
Sure - I suppose this could go under a new category of integration modules - resilience (just as we have observability, logging etc.)
Don't worry about 0.x versions - it core that is guaranteed to be stable, other modules generally follow the lifecycles of whatever they are integrating with