> Want to run a message bus? AWS will make your head spin with SNS, SQS, Kinesis, Kinesis Streams and Kinesis Firehose. GCP has only Pub/Sub which just works and is insanely scalable.
This point is oddly weak in comparison to the others.
> Amazon has one of the most confusing IAM. While it is nice to set up a role to only allows usage for a particular resource from a specific device and times of day, you end up spending most of your time debugging policies.
Haven't used GCP, but I didn't mind IAM. Missed it when I waas trying to figure out Azure stuff.
> We moved because we wanted to work on infrastructure that runs YouTube, Gmail and Google Analytics. We moved because Google is fair, much more tech-savvy and launch products that just works.
ugh. Perfectly fine article now just reeks of google "fanboy-ism".
> This point is oddly weak in comparison to the others.
Agreed - it was senseless. SNS/SQS aren't particularly complex and they scale like crazy. Kinesis is something else entirely (N-hour record retention w/arbitrary consumers and offsets) and doesn't even belong in the comparison.
> ugh. Perfectly fine article now just reeks of google "fanboy-ism".
Do Google's core products actually run on GCP these days? I was under the impression they do not.
This point is oddly weak in comparison to the others.
> Amazon has one of the most confusing IAM. While it is nice to set up a role to only allows usage for a particular resource from a specific device and times of day, you end up spending most of your time debugging policies.
Haven't used GCP, but I didn't mind IAM. Missed it when I waas trying to figure out Azure stuff.
> We moved because we wanted to work on infrastructure that runs YouTube, Gmail and Google Analytics. We moved because Google is fair, much more tech-savvy and launch products that just works.
ugh. Perfectly fine article now just reeks of google "fanboy-ism".