Re:Myths about platform engineering: what it is and what it ...
by victor106 on Friday May 31, 2024 @12:42PM
(#40537282)
I agree. Use all three and Azure is the worst.
Re:Myths about platform engineering: what it is and what it ...
by pjmlp on Friday May 31, 2024 @01:59PM
(#40538335)
At least Azure has UI workflows for everything that is also exposed via AZ, Powershell, ARM and bicep.
Nothing like tracking down what magic spell is needed to reveal on the CLI features not exposed on dashboards.
Re:Myths about platform engineering: what it is and what it ...
by coredog64 on Saturday June 01, 2024 @11:46AM
(#40546688)
My AWS pet peeve is that there are edge cases where the console does some bit of magic but the AWS CLI team is allergic to including it.
Protip: If it’s useful enough to appear on the console, it’s useful enough for the command line.
Re:Myths about platform engineering: what it is and what it ...
by lenkite on Sunday June 02, 2024 @08:26AM
(#40553554)
Only once you have invested significant effort in implementing all the failure-handling and retry mechanisms in your code, then Azure works smoothly.
Re:Myths about platform engineering: what it is and what it ...
by jwnin on Friday May 31, 2024 @04:17PM
(#40539744)
May be personal preference, or what you experienced first, but I prefer Azure with AWS as a close second, GCP as a distant third.
I find that AWS is overly account-focused, and it's more difficult to do operations at an org level. Azure is the inverse.
But I also don't like how Azure PaaS/serverless deploys open to the Internet by default.
That said, I prefer GCP as a product to AWS (and don't even get me started on Azure).