Yep -- still working on cloudy stuff :)
The good news here is that Google Cloud is super similar to AWS (I think we can all agree AWS has done a pretty stellar job designing stuff that solves people's hosting problems). This means that most AWS products have a Google counterpart (S3 -> Cloud Storage, EC2 -> Compute Engine, Beanstalk -> App Engine w Managed VMs, RDS -> Cloud SQL).
Here's a few differences you'll notice using Google vs AWS off the top of my head...
(This is coming from the perspective of a very happy and very large former AWS customer -- we built Invite Media on AWS, and our bill in 2012 was about ~2m USD per month which was a few thousand EC2 machines, a Petabyte of storage on S3, etc.)
- Google VMs will likely be cheaper than AWS
- AWS has way more geographical choices for your VMs to live today
- Both Google and AWS storage is optimized for high scale, throughput, and durability, however Google chooses availability whereas AWS chooses latency. This means that if an AWS region goes down, DynamoDB goes down, whereas if a Google Cloud region goes down, Datastore keeps running just fine. The trade off is that Dynamo is super fast, and Datastore is not.
- AWS has more infra services than Google today (Elasticache, IOT, etc)
- Google has some really nifty unique services today (ie, BigQuery -- which is insanely fast and really cool, and the Vision API which gives you back metrics like "there's a face at position x, with a likelihood of [joy, anger, surprise] of y%" -- to me that's kind of crazy cool)
Anyway -- short version is they're both good. Amazon has been in the external-facing game since ~2007, Google's been in this game internally since ~2004, but externally only since ~2013 (excluding App Engine)...
Some links to read in case you think I'm full of shit: