Hello,
I was reading your article and you mentioned:
You can also implement the exponential backoff algorithm to handle the retries more efficiently.
However, I noticed that your library doesn’t currently offer a way to implement exponential backoff for retry logic. I think this would be a valuable addition, especially since there are already numerous implementations of functions called lazyWithRetries with exponential backoff available on the internet. It seems like it would be relatively straightforward to integrate this functionality into your library.
I’d love to know your thoughts on whether you believe it would make sense to add this feature, or if there was a specific reason for leaving it out. Perhaps there’s an architectural choice or design philosophy behind the decision?
Thanks in advance for your feedback!
Hello,
I was reading your article and you mentioned:
However, I noticed that your library doesn’t currently offer a way to implement exponential backoff for retry logic. I think this would be a valuable addition, especially since there are already numerous implementations of functions called
lazyWithRetrieswith exponential backoff available on the internet. It seems like it would be relatively straightforward to integrate this functionality into your library.I’d love to know your thoughts on whether you believe it would make sense to add this feature, or if there was a specific reason for leaving it out. Perhaps there’s an architectural choice or design philosophy behind the decision?
Thanks in advance for your feedback!