Couple of years ago us-east was considered the least stable region here on HN due to its age. Is that still a thing?
When I was there at aws (left about a decade ago), us-east-1 was considered least stable, because it was the biggest.
I.e. some bottle-necks in new code appearing only _after_ you've deployed there, which is of course too late.
It didn't help that some services had their deploy trains (pipelines in amazon lingo) of ~3 weeks, with us-east-1 being the last one.
I bet the situation hasn't changed much since.
>It didn't help that some services had their deploy trains (pipelines in amazon lingo) of ~3 weeks, with us-east-1 being the last one.
oof, so you're saying this outage could be cause by a change merged 3 weeks ago?
Couple of weeks or months ago the front page was saying how us-east-1 instability was a thing of the past due to <whatever chang of architecture>.
Yup, never add anything new to us-east-1. There is never a good reason to willingly use that region.
Yes
When I was there at aws (left about a decade ago), us-east-1 was considered least stable, because it was the biggest.
I.e. some bottle-necks in new code appearing only _after_ you've deployed there, which is of course too late.
It didn't help that some services had their deploy trains (pipelines in amazon lingo) of ~3 weeks, with us-east-1 being the last one.
I bet the situation hasn't changed much since.
>It didn't help that some services had their deploy trains (pipelines in amazon lingo) of ~3 weeks, with us-east-1 being the last one.
oof, so you're saying this outage could be cause by a change merged 3 weeks ago?
Couple of weeks or months ago the front page was saying how us-east-1 instability was a thing of the past due to <whatever chang of architecture>.
Yup, never add anything new to us-east-1. There is never a good reason to willingly use that region.
Yes