Exponential Backoff in Golang

[aklepatc]

https://go.dev/play/p/sFjrKyGmd0y

TODO: add some meaningful test logic.

Comments

[juan_gandhi]

I woult not use an integer multiplier. sqrt(2) is a better one, based on my experience.

[aklepatc]

Ty for this!

I thought about something like 2 for the multiplier. But I can see how fractional one makes (more?) sense.

[aklepatc]

Is there some mathematical justification for sqrt(2) value specifically? Or did you just empirically decide on something between ~1.4 and ~1.5?

[juan_gandhi]

Empirically. Tested in practice, while implementing either ZModem or Kermit. User shuba_duba worked on this.

[sassa_nf]

nit: callback might want the ctx, too

[aklepatc]

Sure. The idea is you cannot have it at the very "bottom" though.

You always end up calling some legacy API which is not interruptible.

[aklepatc]

The callback is intended to represent something heavy weight, clumsy, unreliable and un-interuptable.

[sassa_nf]

Shipit!

[aklepatc]

Oh, I already failed at that (figuratively speaking). This coding exercise is the end result of an interview that resulted in rejection. Lol.

I do hope to reuse the approach in the future though.