Applying retry strategies on API calls to make them more robust often brings its own set of problems. Occasionally, rather than losing an entity-creating call, you end up with multiple, and trust me — duplicates are a pain to clean up.
However, idempotency can neutralise the inconveniences from retries, making the pair a powerful combo. 💪
With this post, I am in deeper waters than usual. What might sound like a recommendation in the following could be a potential disaster in disguise. Be warned.
Personally, I prefer not to know about implementation details about the function I’m calling. Although that was the situation I suddenly found myself in, when a function I call replaced map with pmap.
Here is how I approached the weirdness with exceptions tangled with pmap.
The last couple of years, I’ve been finding stress at work more often than I’d like. Apparently, experiencing problems, having the skill to address it, but not being allowed to, is something that really gets to me.
So much that I don’t even feel like working on side projects, open source and writing posts on my blog.
The posts touch a lot of different topics in no particular order. It might be more convenient to browse by tags if you have a topic of specific interest.