It's interesting that you call Azure the default stack. That sort of proves my point.
AWS is the default cloud stack. It's more mature, more companies run on AWS than on any other cloud platform, it has full .NET and .NET Core support, it even supported things like .NET Core or F# much earlier than Azure did. There is more resources online, more courses, more talent and more books on AWS than on any other cloud platform.
So how is Azure the default stack? You call it default, because Microsoft has spend so much marketing - aka educating you - to believe that Azure IS THE DEFAULT thing to use.
It's sad honestly, because it makes .NET development a lot less fun and I really like .NET otherwise.
EDIT:
Comment below me:
> I think rather because it is integrated into Visual Studio and SQL Management Studio out of the box.
This is another example that precisely proves my point, that .NET devs have been educated to stop looking beyond what Microsoft puts on their plate.
AWS also has fantastic Visual Studio support. It's only one plugin away. It's like installing a NuGet package, hardly any effort. But the default .NET developer rather uses an inferior cloud stack, because the effort to install an AWS plugin into Visual Studio is seen as more effort than having to deal with all the inabilities of Azure in the long run. That doesn't make sense. It's irrational and only because Microsoft has done such a great marketing it doesn't even occur to the majority of .NET devs.
You can deploy code anywhere, and all 3 major clouds have good tooling for it. Azure is obviously more integrated since it's also from MS but that's completely unsurprising and has no impact on your choices.
AWS is the default cloud stack. It's more mature, more companies run on AWS than on any other cloud platform, it has full .NET and .NET Core support, it even supported things like .NET Core or F# much earlier than Azure did. There is more resources online, more courses, more talent and more books on AWS than on any other cloud platform.
So how is Azure the default stack? You call it default, because Microsoft has spend so much marketing - aka educating you - to believe that Azure IS THE DEFAULT thing to use.
It's sad honestly, because it makes .NET development a lot less fun and I really like .NET otherwise.
EDIT:
Comment below me:
> I think rather because it is integrated into Visual Studio and SQL Management Studio out of the box.
This is another example that precisely proves my point, that .NET devs have been educated to stop looking beyond what Microsoft puts on their plate.
AWS also has fantastic Visual Studio support. It's only one plugin away. It's like installing a NuGet package, hardly any effort. But the default .NET developer rather uses an inferior cloud stack, because the effort to install an AWS plugin into Visual Studio is seen as more effort than having to deal with all the inabilities of Azure in the long run. That doesn't make sense. It's irrational and only because Microsoft has done such a great marketing it doesn't even occur to the majority of .NET devs.