Okay, but as a heavy customer of AWS for 10 years and Azure & GCP for 6 years... there's some very valid criticism of the capacity planning and elasticity.
I hit capacity, provisioning and scaling issues all the time in Azure regions. And many times the cause is not obvious because most services seem to be unaware that the resources are exhausted, and fail with seemingly unrelated errors and partial failure.
edit: and to be fair, I'm not saying it's easy to build something like Azure or that I would do better. And I have a huge list of cases where Amazon's product engineering is terrible compared to Azure's. But... the problems I've seen all week in the UK aren't imaginary. I've had no such problems on Amazon.
Indeed. Getting quota increases is also a much slower and involved process, compared to AWS or GCP.
> and fail with seemingly unrelated errors and partial failure.
Oh, don't get me started! If managers were forced to work with the Azure API, they would not choose it as the provider. The unclear error responses are the most aggravating part.
Azure clearly prioritized massively increasing their geographic footprint without the availability zones that AWS almost always deploys when they enter a new region, and I have no doubt they run leaner with less compute available then AWS.
When I was on the telemetry team about 3 years ago, we were in the early days of transitioning from the internal only "physical cloud" that the Bing team had created years before into Azure, and it was full of pain for a service our size at that time.
Based on my experience, Azure is not as good at AWS and Google at actually keeping things up and running when the shit hits the fan. And AWS is not as good as Google. (That said, AWS exposes a lot more to customers than Google does. Google may stay up, but I prefer running software in the AWS cloud.)
That isn't to say that all three aren't doing a lot right. Clearly they all are. And clearly they are all doing a lot right that I don't know how to do. But the fact that they do a lot right doesn't mean that they are equal.
The incident last week was due to hardware failure and completely unrelated to Capacity or COVID. https://status.cloud.google.com/incident/zall/20002
Ugly, but transparent compared to AWS.
But which has had more outages in the last 5 years?
So maybe there are less of them on a per service basis compared the AWS, but when they do happen they are far more serious.
The only AWS has had that came close was the us-east-1 s3 outage. But even that didn't break networking to running instances.
Same thing during the early Office 365 days. These systems were rough.
Zoom and AWS seem to be handling scaling pretty well - I'm a bit confused though as to how much extra capacity it would make sense for AWS to be carrying or maybe they aren't being asked to scale the way microsoft is which is my guess.
AWS has a crapton of capacity. So much so that they were the first ones to come up with the 'spot' instance concept. We could easily get hundreds of spot instances most days, even in a popular region like US-West 2. Those were relatively big ones too, with a minimum 16 VCPUs and 64GB – but given the spot pricing, we would request even bigger ones if they were available. Even when they were terminated, usually we would get a replacement instance in a few minutes. Even faster if the fleet request was flexible and didn't need a particular instance type.
AWS will also honor pretty large quota increases without batting an eye, while Azure (and sometimes even GCP) would send similar numbers "for review" and take their sweet time.
I can only remember a couple of times, years ago, where requests for normal, on-demand instances failed to get satisfied, in a particular availability zone. But the other zones would be fine.
Most Azure regions do not even _have_ availability zones, so that's out.
Teams was used before but suddenly in my company you had 100k office workers working from home and all meetings converted to Teams meetings, a lot with video streaming. People also seem to react by booking even more meetings now when the casual talk was gone (instead of chatting casually).
I don't know the exact numbers but I'm pretty sure the rise in popularity of Zoom is just as high, if not possibly higher, than Teams. Entire universities of 50k+ students started using Zoom for online classes, not to mention all of the companies that have started using it. Then you have all of the people staying at home using the streaming services, etc... my guess is that AWS has seen a huge spike in traffic just as big, if not bigger than Azure saw.
https://www.theverge.com/2020/3/19/21186452/microsoft-teams-...
Zoom does not release numbers but they have seen an increase say in usage but if we look at estimated numbers:
>Zoom had 12.92 million monthly active users, up 21% since the end of 2019, Chrane and Isaacs wrote, citing data from privately held Apptopia.
https://www.cnbc.com/2020/02/26/zoom-has-added-more-users-so...
Microsoft seems to have had an increase that similar to Zoom's whole user base in a week (and I don't know how much was added before that).
I think people in tech circles underestimate how many large non-tech companies just followed Microsoft into the cloud and started to use Office 365. And I assume a lot don't use it that much, maybe for a meeting here and there and a few (or way too many) channels but suddenly everyone in the company is on it.
Zoom released some numbers a couple of days ago:
“To put this growth in context, as of the end of December last year, the maximum number of daily meeting participants, both free and paid, conducted on Zoom was approximately 10 million. In March this year, we reached more than 200 million daily meeting participants, both free and paid.”
https://blog.zoom.us/wordpress/2020/04/01/a-message-to-our-u...
I have so many bad experiences with limit increases on AWS.
I just went through one trying to get concurrent AWS Lambda executions increased from the default 1.000 in a region to 10.000. I had to open a support case, fill out an optional questionnaire (which turned out to be not optional at all), the support engineer had to forward the questionnaire to the AWS Lambda service team and they came back a few days later with: oh, you can have 5.000 concurrent executions.
Even worse a few years ago (not sure if that's still the case) we tried to get an increase of the sum of storage available as EBS-volumes. That took quite a bit back and forth with AWS and in the end we learned that they do reserve such EBS-storage for a customer no matter if the customer uses it or not. And mind: We didn't request something like guaranteed available EBS-storage, but instead just the ability to request more storage.
EC 2 and ELB increases are relatively easy to come by, but for some services like Media Services things has to get reviewed by the service team which can take a while.
Uh, as a former Microsoft equivalent of a SRE this is a utterly ridiculous statement.
I was in the Windows division on a team handling all the incoming telemetry - we definitely knew how to prepare for traffic surges and keep our services "always on".
Has the author never seen Office 365? Bing? The entirety of Azure in general that has dozens if not hundreds of publicly facing always on services?