[PeterHK]

for sure all of them have pros/cons.

i have been using AWS for many years across multiple companies now. Over the years i got the feeling that the quality has degraded. New services are half-baked (ES, EKS), some newer API's are overly complicated (VPC peering is overloaded for cross-account AND internal instead of 2 abstractions on top of it - why do i need to get confused about all these extra API args which are not needed for internal VPC peering and have to spend hours to finally understand it). Overall AWS feels that they got more sales focused.

i just started to get nightmares with Azure recently, luckily i was able to get rid of almost everything of it (only keyvault remains, since azure does for now have the best offering for HSM). The UI is absolute terrible from front-end caching bugs to strange permissions. MS seems to have to invent their own vocabulary for everything instead of using terminology that most of the rest of the internet uses (which makes finding things very hard), same goes for their API's, its almost impossible to use their API's without these super huge and often buggy libs (try to use REST API auth without a lib...). I am personally also having a hard time to read their documentation.

I did not had the chance to try GC yet but i want to. I know that google services sometimes can be a bit complex to start with, but there is good documentation and reference docs - its usually very easy to just use REST api if you dont wanna use some heavy libs. We recently moved to k8s (i am loving it - continues deploying apps with autoscaling and 0 downtime was never that easy), so as we move more into k8s i hopefully get the chance to try out GC