5 ms·
I've worked extensively with both GCP and AWS. I've met many Google engineers, TAMs, etc. and I wholeheartedly agree with your sentiment. That said, I prefer G
by cassianoleal 2y ago
I've worked extensively with both GCP and AWS. I've met many Google engineers, TAMs, etc. and I wholeheartedly agree with your sentiment.
That said, I prefer GCP as a product to AWS (and don't even get me started on Azure).
- jwnin 2y agoMay 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.
- nosefrog 2y agoYou prefer Azure? Things on Azure don't work by default.
- victor106 2y agoI agree. Use all three and Azure is the worst.
- lenkite 2y agoOnly once you have invested significant effort in implementing all the failure-handling and retry mechanisms in your code, then Azure works smoothly.
- pjmlp 2y agoAt 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.
- coredog64 2y agoMy 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.