Fault tolerance and resilience patterns for Go

If I&#x27;m allowed to make a critique, I&#x27;d say that the module doesn&#x27;t look very much like Go. The (ab)use of generics and having every policy to its own package feel a little over-engineered.<p>I might be slightly biased, because, not knowing about this project, I implemented half of the functionality in my own simpler module: <a href="https:&#x2F;&#x2F;git.sr.ht&#x2F;~mariusor&#x2F;ssm" rel="nofollow">https:&#x2F;&#x2F;git.sr.ht&#x2F;~mariusor&#x2F;ssm</a>

Used the Java version (<a href="https:&#x2F;&#x2F;failsafe.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;failsafe.dev&#x2F;</a>) of this library a few times. It&#x27;s been around for a number of years. Works great!<p>Glad to see a Go version.

Very popular .NET library that does this is <a href="https:&#x2F;&#x2F;github.com&#x2F;App-vNext&#x2F;Polly">https:&#x2F;&#x2F;github.com&#x2F;App-vNext&#x2F;Polly</a>. It seems failsafe borrows heavily from it given first Polly version was released more than 10 years ago.

This is all great except it’s all in memory. To really fail safe you need to account for crashes and therefore need a persistent queue

There&#x27;s this feeling of fulfillment when what you pray for comes true i just want to appreciate this great spy agent (arpanethack @gmail dot com)at first, his first job for me wasn&#x27;t successful and i got refunded back but,i had to give him benefit of the doubt to track my husband&#x27;s phone and it was a success and all information was wired to my phone

For anybody interested in this topic, “Release it!” is a pretty good read. (Not affiliated in any way, just enjoyed reading it)<p><a href="https:&#x2F;&#x2F;www.oreilly.com&#x2F;library&#x2F;view&#x2F;release-it&#x2F;9781680500264&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.oreilly.com&#x2F;library&#x2F;view&#x2F;release-it&#x2F;978168050026...</a>

what does OTP mean in the comments here?

I feel like 2&#x2F;3s of posts on here are people spending tremendous amounts of effort recreating OTP (things Erlang&#x2F;Elixir already does natively).

Was it a bad design decision to not include nullable types in Go?<p>I can&#x27;t count how often I&#x27;ve seen this:<p>Go: panic: runtime error: invalid memory address or nil pointer dereference