Let&#x27;s look at Google vs AWS from people&#x27;s time:<p>* Ease of use: Google Wins(Cloud Shell, SSH into instance from browser). Its far easier to spin up an instance and manage it on Google Cloud than AWS with VPC mess.<p>* Platform Cohesivity: Google Wins (See the comparisio below)<p>* AWS has 2 storage solutions with different APIS: S3 and Glacier; Compare that to Google. Just one storage solution to serve all needs. You get a backed in CDN for free!<p>* AWS has two queuing systems (SQS and Kinesis) and still require the developer &#x2F; admin to adjust the scaling of infrastructure. Google has just one Pub&#x2F;Sub. You get push notifications on top. No need to tune knobs to get extra scale. It just works.<p>* AWS load balancers and persistent disks need warming up before high usage. If you are running a website on global scale, you need to use DNS geo load balancing on top. Google load balancers are global (as opposed AWS regional load balancers), no need of DNS tricks. No need of prewarming. Google persistent disks need no prewarming. You can mount a single persistent disk on multiple instance and share data easily.<p>* Security: Google encrypts data at rest and at wire by default. Try doing that on AWS. Google takes care of SSH key provisioning and management. AWS: You have to do it by yourself.<p>* AWS NATs and micro instance are known to be unreliable. Google has live migration. If something goes wrong with instance they work their magic behind the scenes so that you don&#x27;t have to worry about migrating the instance to another physical host.<p>* Automation: Instance id are not global on AWS. Have fun creating maps and stuff inside CloudFormation templates. Google Cloud resources are global. All resources (images ids) have a global identifier. No more messing with zonal vs regional vs global resources.<p>Google Cloud can save money by saving your time too!