I wonder how many companies have properly designed their clients. So that the timing before re-attempt is randomised and the re-attempt timing cycle is logarithmic.
In short, if it’s all at the same schedule you’ll end up with surges of requests followed by lulls. You want that evened out to reduce stress on the server end.
It's just a safe pattern that's easy to implement. If your services back-off attempts happen to be synced, for whatever reason, even if they are backing off and not slamming AWS with retries, when it comes online they might slam your backend.
It's also polite to external services but at the scale of something like AWS that's not a concern for most.
I had to try several different straps and configurations before I found one that worked well for me. I forget what it's called now, but there's one made by a company that makes CPAP machines. That's the one to get. Makes a huge difference.
A bit off topic. But I never understood these country staggered releases that some companies, like Anthropic, does. The country list seems completely random.
He claims to not have any bias whatsoever and be an absolute centrist, which leads to him being a pawn on whatever his guests want to promote while also asking the most awful, bland questions he can possible think of
Although you could say that the outcome could be considered the same, the motivations behind it are completely different, as the parent comment mentions
I tend to watch a lot of MIT open courseware, most of the times not really paying that much attention. But this professor (Andrew Lo) is the best one by far. Makes the syllabus really engaging and easy to understand