you are viewing a single comment's thread
view the rest of the comments
[–] 60 points 1 year ago (8 children)

It's mostly a skill issue for services that go down when USE-1 has issues in AWS - if you actually know your shit, then you don't get these kinds of issues.

Case in point: Netflix runs on AWS and experienced no issues during this thing.

And yes, it's scary that so many high-profile companies are this bad at the thing they spend all day doing

  • source
  • parent
  • hideshow 8 child comments
  • [–] 20 points 1 year ago (3 children)

    Yeah, if you're a major business and don't have geographic redundancy for your service, you need to rework your BCDR plan.

  • source
  • parent
  • hideshow 3 child comments
  • Absolutely this. We are based out of one region, but also have a second region as a quick disaster recovery option, and we have people 24/7 who can manage the DR process. We're not big enough to have live redundancy, but big enough that an hour of downtime would be a big deal.

  • source
  • parent
  • [–] 4 points 1 year ago (1 child)

    What's the general plan of action when a company's base region shits the bed?

    Keep dormant mirrored resources in other regions?

    I presumed the draw of us-east-1 was its lower cost, so if any solutions involve spending slightly more money, I'm not surprised high profile companies put all their eggs in one basket.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 1 year ago

    I presumed the draw of us-east-1 was its lower cost

    At no time is pub-cloud cheaper than priv-cloud.

    The draw is versatility, as change didn't require spinning up hardware. No one knew how much the data costs would kill the budget, but now they do.

  • source
  • parent