One of the big advantages of Google Cloud platform is "Scalability".

Load balancers: Scale to millions of users seamlessly. No warming up, no tickets, ...

PubSub: You can send the whole Internet 10 times in a day through it. Google does that every day

Big Query: Its equivalent to spinning up a 100+ node cluster in a matter of seconds and it can process data at speeds of GB's of data per sec, I heard couple of use cases where the user was able to process at ~ 50 GB/s

Kubernetes: 1000's of nodes running 100's of thousands of containers.

Can't beat that!

Sounds expensive when no one is looking at how the magic works.

> You never know what you don't measure and test

Funny you should mention that. :) I work at Google on PerfKit Benchmarker (https://github.com/GoogleCloudPlatform/PerfKitBenchmarker). Not only can you measure and test GCP (and other clouds), but we're trying to make it very easy for you to do so!

(PKB doesn't have a benchmark for App Engine yet, though. Sorry.)

Speaking for latchkey here (I'm the other guy), we routinely run several-thousand-qps batch jobs. Scalability is not an issue.

Are you implying that we don't measure and test? We do and I'm very happy with the results. =) StackDriver, Google Cloud console, Intercom, Mixpanel and Pingdom are all being used as well.

If that's the case then you might actually be "doing devops". If pingdom is notifying you via sms then you may also be carrying a pager.

Touché -- That said, we don't have pinggom tied to SMS, just email. =) Pingom is just an external tool for us to graph uptime from other parts of the world.

If we're down there is plenty of other alerting to notify us (mostly through Slack). That said, there isn't much we can do other than wait for Google to fix it.

It is part of the trade off that we have to consider, I'm paying Google for devops instead of paying a team to do it for me. If you've ever had to hire a 24/7 support/devops staff, it is a much easier hiring proposition to just rely on Google to do that for us.

> That said, there isn't much we can do other than wait for Google to fix it.

IE. "Cloud ops"

Indeed, I do wish we'd stop with all of the verbal gymnastics and just say we're doing ops correctly. "We don't do ops" usually means "We don't find ops to be troublesome because we do it correctly". No group of people needs dedicated janitorial staff if everyone picks up and dusts occasionally. Of course, you know what this implies.