Microsoft had three staff at Australian data centre campus when Azure went out

Post by lithos » Tue, Sep 05, 2023, 12:19 PM UTC

mtmail wrote: post #18

22c wrote: post #8

Earlier quoted context omitted.

0 - 2 staff in a typical DC is not unusual at all, with people who are on-call usually within a 30 minute drive. Larger DCs can and do have more staff on-site 24/7 and typically the amount of staff on-site at any given time is driven by SLAs. I expect the DC in TFA to return to lower staff levels once they've worked on reducing their total "time to restart chiller" or reduced the amount of manual work involved in doi…

Still we read how DCs are a job generator. E.g. "One hopes for hundreds of jobs for locals." https://cryptoquorum.com/oman-opens-cryptocurrency-mining-ce...

Yeah Northern Virginia trapped themselves with that thinking. They can't stop building Datacenters, less they lose tens of thousands of jobs in the region. And the Datacenters know this, that they can beat concessions out of politicians for it.

Post by dalyons » Tue, Sep 05, 2023, 10:20 PM UTC

traceroute66 wrote: post #49

dalyons wrote: post #38

Earlier quoted context omitted.

Also the vast array of managed services. Managed databases, message queues, infinite storage, data warehouses, caches , etc etc. Many of which are very complicated to host well yourself and operationize (failovers, monitoring , backups etc) This idea that you can build a DC that competes on cost for rented cloud compute - it might be technically true but it’s mostly missing the point of why modern shops prefer the cl…

> Many of which are very complicated to host well yourself and operationize (failovers, monitoring , backups etc) Oh you are hilarious. Time for your daily reminder that failovers, monitoring and backups DO NOT EXIST in the cloud UNLESS (a) you configure and manage them (b) deploy your services in multiple zones (and spend $$$$$ along the way). Lots of people cannot do (a) properly and it is regularly demonstrated by…

hey maybe avoid the patronizing crap? I've been involved in running at-scale properties in the cloud and not for 20 years or so now so, whilst i dont know everything i do somewhat know what im talking about.

Making an RDS postgres instance multi-az with automatic failover, and bulletproof backups to s3 is ticking a couple of boxes. Compared to building all of that yourself at the same level of uptime - its not complexity of the same magnitude at all. And sure it will cost you more for the instances for redundancy, but its pretty easily worth it - i dont have to pay an ops team to babysit my databases. Thats just postgres - not even getting into things like aurora, dynamo, kinesis, sqs, lambda - things that either dont have a self-hosted equivalent at all, or if they do are way more complicated to run at scale than PG.

In some cases its trading cloud costs for personnel costs. Both opex. But in many others its having access to services, datastores etc that i couldnt otherwise have as a dev.

Re: Microsoft had three staff at Australian data centre campus when Azure went out

Re: Microsoft had three staff at Australian data centre campus when Azure went out