Hi guys, I'm the original poster. Sorry for joining so late. I read each and every feedback and also updated the medium article. In no particular order: 1) Did

Hi guys, I'm the original poster. Sorry for joining so late. I read each and every feedback and also updated the medium article. In no particular order: 1) Didn't mean to hand-wave. For the last few months GCP was the new shiny toy for me. I got over excited and plan to do deeper post, battling 2 or more products (i.e Kinesis vs. Pubsub) 2) Not anti-AWS at all. I still find it wonderful: https://lugassy.net/search?q=aws https://lugassy.net/search?q=aws. what really flipped me was this: https://twitter.com/mluggy/status/727764607176159232 https://twitter.com/mluggy/status/727764607176159232 and other small anonyances 3) Downsides to GCP. Certainly! added to the article 4) For developers, by developers. I realize this was tacky. Let me try again with 4 examples: a) Trace/breakpoints in production b) Connecting through virtual socket files instead of tcp c) writing and collecting logs centrally with console.log and specifically d) DATAFLOW which is architecturally brilliant (AWS add "Streams" to every new product where GCP simply treat every product as source and/or sink) 5) Yes I favor GCP for simplicity and dev-friendliness. I don't want to train people for AWS devops/gotchas. I don't need sophisticated IAM and VPC to feel smart. GCP ui/quickbar is nicer. For example networking is all on one page. Most products are properly named (CDN instead of CloudFront, DNS instead of Route53, Pub/Sub instead of Kinesis) 6) GAE. I was exposed to some horror stories about its and datastore early days. History aside, I use it today through Flexible VMs which is really docker under the hood + ability to SSH + easy deployment/versioning + cool tracer/debugger. My code is Node.js and haven't coded any GAE specific necessity Again loved the comments. keep it going!