| ▲ | yibers 5 hours ago |
| Ass covering-wise, you are probably better off going down with everyone else on us-east-1. The not so fun alternative: being targeted during an RCA explaining why you chose some random zone no one ever heard of. |
|
| ▲ | rconti 4 hours ago | parent | next [-] |
| Places nobody's ever heard of like "Ohio" or "Oregon"? Yeah, I'm not worried about being targeted in an RCA and pointedly asked why I chose a region with way better uptime than `us-tirefire-1`. What _is_ worth considering is whether your more carefully considered region will perform better during an actual outage where some critical AWS resource goes down in Virginia, taking my region with it anyway. |
| |
| ▲ | xingped 3 hours ago | parent [-] | | IIRC, some AWS services are solely deployed on and/or entirely dependent on us-east-1. I don't recall which ones, but I very distinctly remember this coming up once. | | |
|
|
| ▲ | kristianc 3 hours ago | parent | prev | next [-] |
| I find it funny that we see complaints about why software quality has got worse alongside people advocating to choose objectively risky AWS regions for career risk and blame minimisation reasons. |
| |
| ▲ | goalieca 3 hours ago | parent | next [-] | | This was always the case. The OG saying was “no one got fired for buying IBM”. Then it was changed to Microsoft. And so on.. | |
| ▲ | 3 hours ago | parent | prev | next [-] | | [deleted] | |
| ▲ | throwawaysleep 3 hours ago | parent | prev [-] | | They are for the same reason. How do customers react to either? If us-east-1 fails, nobody complains. If Microsoft uses a browser to render components on Windows and eats all of your RAM, nobody complains. | | |
| ▲ | bigstrat2003 28 minutes ago | parent [-] | | Oh, people complain. The companies responsible have just gotten to the point where they are so entrenched that they don't need to care at all about customer complaints. | | |
|
|
|
| ▲ | jordanb an hour ago | parent | prev | next [-] |
| Istr major resource unavailability in US-East-2 during one of the big US-East-1 outages because people were trying to fail over. Then a week later there was a US-East-2 outage that didn't make the news. So if you tried to be "smart" and set up in Ohio you got crushed by the thundering herd coming out of Virginia and then bit again because aws barely cares about you region and neither does anyone else. The truth is Amazon doesn't have any real backup for Virginia. They don't have the capacity anywhere else and the whole geographic distribution scheme is a chimera. |
| |
| ▲ | Fhch6HQ an hour ago | parent [-] | | This is an interesting point. As recently as mid-2023 us-east-2 was 3 campuses with a 5 building design capacity at each. I know they've expanded by multiples since, but us-east-1 would still dwarf them. Makes one wonder, does us-west-2 have the capacity to take on this surge? |
|
|
| ▲ | nothrabannosir 2 hours ago | parent | prev | next [-] |
| > being targeted during an RCA explaining why you chose some random zone no one ever heard of. “Duh, because there’s an AZ in us-east-1 where you can’t configure EBS volumes for attachment to fargate launch type ECS tasks, of course. Everybody knows that…” :p |
|
| ▲ | riffic 5 hours ago | parent | prev | next [-] |
| how about following the well-architected framework and building something with a suitable level of 9s where you can justify your decisions during a blameless postmortem (please stamp your buzzword bingo card for a prize.) |
| |
| ▲ | paradox460 4 hours ago | parent [-] | | We vibe code everything in flavor of the month node frameworks, tyvm, because elixir is too hard to hire for (or some equally inane excuse) | | |
| ▲ | DANmode 4 hours ago | parent [-] | | I agree with your post conceptually. However: Don’t underestimate community support (in the areas you’re likely to want it) when comparing development stacks. |
|
|
|
| ▲ | throwawaysleep 4 hours ago | parent | prev | next [-] |
| This to me was the real lesson of the outage. A us-east-1 outage is treated like bad weather. A regional outage can be blamed on the dev. us-east-1 is too big to get blamed, which is why it should be the region of choice for an employee. |
| |
| ▲ | Esophagus4 2 hours ago | parent | next [-] | | Bizarre way of making decisions. us-east-2 is objectively a better region to pick if you want US east, yet you feel safer picking use1 because “I’m safer making a worse decision that everyone understands is worse, as long as everyone else does it as well.” | | |
| ▲ | nemomarx 2 hours ago | parent | next [-] | | It's about risk profile. The question isn't "which region goes down the least" but "how often will I be blamed for an outage." If you never get blamed for a US east outage, that's better than us-east-2 if that could get you blamed 0.5% of the time when it goes down and us1 isn't down or etc | |
| ▲ | TheNewsIsHere an hour ago | parent | prev [-] | | I also don’t understand this. US-East-2 staying up isn’t my responsibility. If I need my own failover, I’m going to select a different region anyway. And it’s not like US-East-2 isn’t already huge and growing. It’s effectively becoming another US-East-1. |
| |
| ▲ | dontdoxxme 3 hours ago | parent | prev [-] | | Why aren't you using IBM cloud? | | |
| ▲ | throwawaysleep 3 hours ago | parent | next [-] | | If IBM still had a good reputation, I probably would. | | |
| ▲ | skissane 2 hours ago | parent [-] | | I’ve seen people go with IBM Cloud because their salespeople were willing to discount more heavily than AWS/GCP/Azure were. Tier 2 players can be hungrier for your business than tier 1 are. And here I’m talking about completely mainstream workloads (Linux, K8S, etc) Separately from that, if you are trying to move certain types of non-mainstream IBM workloads to cloud (AIX, IBM i, z/OS) then IBM is tier 1 in that case |
| |
| ▲ | 3 hours ago | parent | prev [-] | | [deleted] |
|
|
|
| ▲ | thejosh 4 hours ago | parent | prev [-] |
| Bandwidth cost is also another major reason. |
