4 ms·
A few interpretations: - Folks on Azure are active-active in multiple availability zones - Most of those using Azure are not impacted by this particular outag
by echelon 5y ago
A few interpretations:
- Folks on Azure are active-active in multiple availability zones
- Most of those using Azure are not impacted by this particular outage
- Azure isn't widely used
...
- jhugo 5y ago> Folks on Azure are active-active in multiple availability zones Why would people on Azure be more likely than people on AWS to have redundancy? Anyway, in the recent AWS outages, multiple AZs didn't help much. Needed to be in multiple regions.
- macksd 5y agoIn my experience, a higher portion of Azure customers are larger enterprise customers that engage professional services from Microsoft to architect things, etc. AWS is far more popular in general, but especially with smaller teams that are more self-directed, start with prototypes and iterate from there. It wouldn't surprise my if the latter often only built in redundancy after learning lessons the hard way, even though AWS provides the ability to do so from the get go. Purely conjecture, but that skew in the customer type is definitely there.
- bfung 5y agoBefore “the cloud”, it was already common to run Active Directory installs as active-active in on- prem scenarios, since those installs would’ve hit outages pretty early after installing AD. Maybe not across data center regions, but AD admins learn real quick to have redundancy and backups. Porting over to Azure AD probably wasn’t such an issue then, as most firms would lift&shift their on-prem to the cloud, keeping the same configurations.
- dylan604 5y agoThis is what I didnt get about the multi-AZ claims. If you're in multiple zones within the same region when that region goes down, you're still going down too. Yet, this seems to be the agreed upon solution decreed far & wide.
- cdegroot 5y agoIt helps. It's not a silver bullet. AZs tend to go down more often than whole regions, is the belief (I don't think there's sufficient data, but a priori it does make sense).
- bob1029 5y agoWe are on Azure but no one was working when this hit and we don't host any critical workloads so its not a big deal for us this time. AWS and GitHub seem to crater right when everyone is using them the most (i.e. 10am EST on a Tuesday), so there is bound to be far more discussion around these occurrences since everyone is wired on coffee, ass-in-chair, frustrated that they can't get any work done. People usually don't get out of bed and then get on the internet to complain about a transient outage that occurred while they were asleep.
- nirushiv 5y ago- People are at home after work?
- logosmonkey 5y agoThis is probably the correct answer. We run a lot of stuff at work on AAD but I don't care, it's 10:45p EST. If I were on our infra team I might care a bit, mostly monitoring to verify it would be up before users start trying to log on tomorrow but otherwise, meh.
- thedougd 5y agoI'd wager that Azure customers tend to run classic workloads as VMs. Those workloads are usually not impacted by API outages. When AWS has API outages, all those Lambdas, autoscaling groups, subscribers to queues and topics, etc have a very bad day.