Re:Google Brass Set 2023 as Deadline to Beat Amazon, Microso...
by deadbunny on Tuesday December 17, 2019 @09:05PM
(#21821093)
Ah yes the "try getting someone from Google on the phone" trope.
I've used GCP at 2 different places. One with a 10k/month spend and another with closer to 200k/month and received the same level of service. In both instances I've had direct access to engineers to get shit fixed when needed, phone/email/gchat.
Re:Google Brass Set 2023 as Deadline to Beat Amazon, Microso...
by mantap on Tuesday December 17, 2019 @10:00PM
(#21821372)
I've had a real person from AWS support proactively reach out to me because of some issue and I have a $1/month spend.
Re:Google Brass Set 2023 as Deadline to Beat Amazon, Microso...
by josteink on Wednesday December 18, 2019 @02:59AM
(#21822809)
So if your monthly GCP-spending exceeds the salary of 2 engineers, you get access to at least 1.
Sounds great!
Re:Google Brass Set 2023 as Deadline to Beat Amazon, Microso...
by 9nGQluzmnq3M on Tuesday December 17, 2019 @11:50PM
(#21821901)
GCP has a free billing chat support open to every customer, big or small. It's open 24/7, they can reverse charges (although obviously you'll need a pretty solid justification for 4 figures), and they'll happily jump on a call if you ask them to.
Re:Google Brass Set 2023 as Deadline to Beat Amazon, Microso...
by hvidgaard on Wednesday December 18, 2019 @03:23AM
(#21822909)
I have no experience with Google support, let alone GCP support. But what I've heard both from inside and from customers, is that unless someone happen to want to help you with your specific problem, it can be a bit of hit or miss situation to get help. Maybe it's different with now GCP, but until I hear first hand experience telling me otherwise, I'm not even considering moving our cloud business to GCP.
We're running production systems making a significant amount of of our revenue, and when, not if, shit hits the fan we need someone with intimate knowledge of the internals to give us undivided attention until it's resolved.
Sometimes it's because we fucked up, sometimes it's the perfect storm of internals working unexpected - all of the time our systems are not working and our customers depend on them for their daily work.
I am _extremely_ dubious you'd ever even get a person on the phone to talk to at Google if your CI/CD pipeline or platform automation had a bug that resulted in thousands of dollars of charges racking up over a weekend. I know people who've done that on AWS and had the entire bill waived, and then had AWS technical people call and help them debug and fix the broken (non Amazon) systems.
I'm not sure there's a company on the planet with a worse reputation amongst devs for "customer service" than Google. Pretty sure they're not going to be winning any developer mindshare on _that_.
If your 5-6 figure ad buying team get a say in which platform you deploy on, maybe _their_ experience with Google's legendary "customer support" is different. Buy the only known avenue for developers to get problems with Google accounts looked into by a human being is pretty much to make as much noise on Twitter/HackerNews as you can and hope some random Googler steps in to help...