3 ms·
Really comes down to usecase / platform. If you are in .NET land then Azure is the better option; having used both it's just a ton easier. The Publish integrat
by evo_9 4y ago
Really comes down to usecase / platform.
If you are in .NET land then Azure is the better option; having used both it's just a ton easier. The Publish integration with Visual Studio, even the free edition, is really nice. You basically download the Publish profile from Azure, import it and that's it. Once you've set that up you can right-click>Publish at will. It's super nice and while I have no doubt you could achieve the same thing on AWS, but you'd have to figure out and setup a ton of things yourself.
- scarab92 4y agoThis is fine for hacking a POC together, but for anything in production I'd want to go the immutable infra route deployed from a CD server, so the visual studio integration doesnt really help. At a high level I'd say, Azure is more coherent and seems to have a clearer technical vision. They achieve this by moving slower and being more willing to deprecate services/apis which dont meet that standard. AWS move quicker, they offer leading edge tech first, which means that it is often more battle tested and reliable, but they dont benefit from having the opportunity to learn from others' mistakes, which means they tend to expose more warts and inconsistencies to end users.
- mejutoco 4y agoExactly. I was reading OP post and, while I can see why it sounds appealing, reminded me too much of using Filezilla to deploy some files to production.
- evo_9 4y agoNah, after a few decades of development you drop the pretense and go with what's easiest / lease friction. And if you can't see why going with Azure when you're a full .NET guy, then I don't know what else to say.