[tstrimple]

> What pisses me off the most about Azure is now they designed it as the 90's view of what a cloud provider is. With Azure you don't just provision a VM or God forbid a web service. No no no. You need to provision an app service plan first

What's funny is you're completely backwards here. Microsoft has a much more modern view of the cloud than AWS where everything is a thin veneer over EC2. Azure started as PaaS first and AWS started as IaaS first and that fingerprint is still all over their products. Building everything in a VM is the most expensive and naive way to adopt the cloud. It's the main reason why complexity and costs blow up. You're building in the cloud wrong and somehow seemed to have missed that a consumption based Function app is the default option and doesn't require an App Service Plan.

[motorest]

> What's funny is you're completely backwards here. Microsoft has a much more modern view of the cloud than AWS where everything is a thin veneer over EC2. Azure started as PaaS first and AWS started as IaaS first and that fingerprint is still all over their products.

Irrelevant. I don't care about either history or revisionism. I care about deploying apps/functions. In AWS each lambda function is a standalone resource, whereas in AWS you need to 1) provisional an app service plan, 2) deploy a function app on said service plan, 3) deploy the actual function. It's nuts.

Same goes for storage. While in AWS you just go ahead and create a S3 bucket, on Azures you have to providion storage accounts and then provision a blob storage container.

> Building everything in a VM is the most expensive and naive way to adopt the cloud.

Azure is more expensive, harder to manage, even more impossible to estimate costs. Making claims about cost as if it makes Azure look good sounds completely crazy.

[tstrimple]

You lie about or cannot figure out basic things in Azure like creating a Function without an App Service Plan. I cannot take anything you say at this point seriously. You're just coming across jaded and spreading misinformation.

[motorest]

> You lie about or cannot figure out basic things in Azure like creating a Function without an App Service Plan.

I recommend you spend a few minutes going through an intro tutorial on Azure Functions. A key topic on Azure Functions 101 is the concept of a plan and how to pick a hosting option. You can start by reading this link:

https://learn.microsoft.com/en-us/azure/azure-functions/func...

Once you read this link, you'll be aware that even in their so-called serverless plan that follows a "serverless billing model" you still have a plan tucked away where you can run multiple function apps in if you really want to.

Even if you pretend this doesn't exist, you need to ask yourself what is a plan and what does it matter to you and why do you care. Do you think that picking a plan does not factor as a concern in Azure?

[everfrustrated]

>Microsoft has a much more modern view of the cloud than AWS where everything is a thin veneer over EC2

You must be joking!

I was looking a various Container Registry products and looked up Azure's recently. It has the following limits (On the premium SKU!): 50Mbps upload, 100Mbps down

What sort of a cloud product has limits like this! What a clown show.

[p_ing]

The footnote points out that those are minimum limits.

https://learn.microsoft.com/en-us/azure/container-registry/c...

[tstrimple]

As noted, those are minimum limits. If there's a clown show, it's you who is hosting it.

[motorest]

> As noted, those are minimum limits. If there's a clown show, it's you who is hosting it.

Do they specify ay SLA other than the minimums? If not, I'm sorry to tell you, but they only offer the minimum and anything over that is a pleasant surprise.