Summary of the AWS Service Event in the Northern Virginia (US-East-1) Region

Re:Summary of the AWS Service Event in the Northern Virginia... by EnlightenedBro on Saturday December 11, 2021 @01:03AM (#29518852)

But what's a good alternative then? What if the internet connection has recovered? And you were at the, for example, 4 minute retry loop. Would you just make your users stare at a spinning loader for 8 minutes?

[ Parent | on HN ]

Re:Summary of the AWS Service Event in the Northern Virginia... by kqr on Saturday December 11, 2021 @01:39AM (#29519002)

Sure, why not?

Or tell them directly that "We have screwed up. The service is currently overloaded. Thank you for your patience. If you still haven't given up on us, try again a less busy time of day. We are very sorry."

There are several options, and finding the best one depends a bit on estimating the behaviour of your specific target audience.

[ Parent | on HN ]

Re:Summary of the AWS Service Event in the Northern Virginia... by xmprt on Saturday December 11, 2021 @01:38AM (#29518996)

I first learned about exponential backoff from TCP and TCP has a lot of other smart ways to manage congestion control. You don't need to implement all the ideas into client logic but you can also do a lot better than just basic exponential backoff.

[ Parent | on HN ]

Re:Summary of the AWS Service Event in the Northern Virginia... by sciurus on Saturday December 11, 2021 @07:19AM (#29520381)

See for instance the client request rejection probability equation at https://sre.google/sre-book/handling-overload/

[ Parent | on HN ]