Thread by @QuinnyPig

I’m not kidding: this @GCPcloud site explains aspects of what @awscloud does better than AWS’s own marketing pages.

https://twitter.com/gregsramblings/status/1245505901873655808

But they get some things wrong!

In a delightful and refreshing change of pace, *I* will correct *Google* in this thread. Let's explore!

The Osaka-Local region contains a single AZ.

This may be needlessly pedantic as they're currently expanding it into a full region--but you are Google and thus pedantry is required to be hired there.

GCP's multi-regional approach is something AWS doesn't do. It empowers some awesome stuff. *BUT*, and this is a big but: it means there's shared control plane between those regions.

We've seen rolling outages take out services all across Google Cloud, but not AWS. Yet.

This is incorrect. While there's some question as to whether or not Lambda@Edge resides in regions or in CloudFront Edge locations, S3 Transfer Acceleration runs on top of CloudFront and uses its POPs.

Let's be clear here: AWS has had roughly 70 pricing changes across 200 services. All but arguably 3 were straight price cuts.

Linking to the AWS pricing calculator is some *glorious* shade by @gcpcloud here. That thing's monstrous.

"We both provide a CLI for working with our services, but @awscloud calls it a CLI, whereas we at @gcpcloud call it an SDK because in very specific edge cases we're way worse at accurately naming things."

Credit where due: I was excited to tear GCP a new one for putting GKE in here, but they resisted the temptation.

This is accurate except for snubbing Route 53 in AWS's "Databases" section.

This screenshot fails re:Invent slide review and won't be allowed onstage until they call Direct Connect by its proper full name of "AWS Direct Connect."

I'm not even slightly kidding. AWS is... precise, with these requirements.

And after that table, the article completes.

Well done to @gcpcloud for not turning this into a marketing attack piece.

Now here's what I'd do to turn it into a marketing attack piece:

Highlight the AWS services for which there is no GCP competition.

Ground Station, Managed Blockchain, Sumerian.

Explain it's because you designed your cloud for "actual work instead of dicking around." (Run that through Google Translate into corporate-speak first.)

But yes--this is a solid, solid piece. I like it better than the last time I looked at @azure's AWS comparison sheet.

AWS of course has no comparison documents that I've been able to dig up.