The biggest problem GCE has is not performance or anything technical - it is the terrible, terrible support that Google offers (or fails to offer).
I'm pretty sure that most people who have used any of Google's pay for services knows just how bad that support can be.
What happens if something goes wrong with your billing on EC2? No problem, you call them up and sort it out.
What happens if something goes wrong with your billing on any Google product? You'll be down for days while attempting to get Google to even acknowledge a problem.
Until Google fixes their support issues, anybody using a Google service for anything business critical needs to be very careful in weighing up pros and cons.
Disclosure: I work for a competitor to both Google/GCE and Amazon/EC2.
I think that this comment is spot-on. Google doesn't seem to understand that the infrastructure business is fundamentally a trust business: as elastic and transient as the cloud can feel, when choosing a foundation, you're making decisions that must stand for years. Not only does Google provide infamously Kafka-esque service when they're down or otherwise unavailable, they have a history of capriciously killing services and/or repricing them -- and one need look no further than the user dissatisfaction over GAE to know that GCE will be lucky to survive its infancy. Indeed, GCE is caught in a nasty catch-22: because of Google's track record of killing tertiary services, the market is very much waiting for it to become primary for Google -- but because the market is waiting, it may well never be. This is a self-fulfilling prophesy that is as obvious to cloud decision makers as it appears to be lost on Google.
Thank you - I couldn't say this better myself. You have captured the essence of a problem with Google - trust.
After GAE and treatment of "non-essential" products under Larry, I have lost the trust in Google as a reliable business partner, regardless of any technical advantages their offerings might have at the moment.
A small shop like ours can't rely on a partner who can change major aspects of a product without any concern for its customers. And when the trouble comes, being left at the mercy of a random Googler who might come to the rescue if you are sufficiently Internet famous is not a recipee for building a stable business.
Thank you, but no thank you. I'll stick with companies who are relentlessly working on improving their products, driving prices down and care about their customers even if their products might be behind in some areas.
Until Google proves that they care and are in this for a long haul, my business goes somewhere else.
Oh, yeah, this applies to personal usage too - good bye Google Reader, my most used Google product...
That was for the GAE. Who is to say a new "price rationalisation" might not come for GCE?
Or that they wont close it down, like they did with Google Code, Google Wave, Google Reader and such, if they change their minds?
Now, I know that what I wrote would be considered FUD if it was for any other company. But in Google's case, it's not that people say FUD about them. It's that FUD is the very thing they emanate themselves!
Or, in other words, in Google's case, the FUD is real.
Hi Ryan, have you seen the recently announced support packages for the Google Cloud offerings? It's a multi-tiered approach, from Bronze (free, online) to Silver (premium, with email support) to Gold (premium, with 24x7 phone support), all the way to Platinum (premium, with a dedicated technical account team). Announcement here:
It's quite funny that I'd have to pay $150/month for the privilege of email support related to "service errors".
It's completely fair to expect customers to solve their own problems, but when the problem is on Google's end, it's beyond outrageous to charge a premium to resolve those.
I agree that it's funny, and would probably be a turn-off to most people. Consequently, I doubt Google cares if many people sign up for that. Back in the early days of GAE, I remember success stories told by some companies. Anyone established businesses building apps that will bring in serious business revenue might just jump to the Platinum Support. I know this means a lot of indie developers might not be excited about this, but perhaps Google just doesn't care since they might be making money off of the big customers...?
Funny considering the main issue we had with EC2 was amazons horrible support. Even spending a lot (lot) per month our only option was to post on the forums and wait. We ended up at Rackspace after a few years of frustrating issues.
From my limited experience - I'm at best on the periphery of dealing with AWS support; I can characterize aws support as such -
Free tier - occasionally get answers. answers are generally vague. questions to forums.
Paid tier - always get answers. answers are generally vague. you get a support portal.
Top tier paid - always get answers. answers are generally vague. amazon employees will fly out to your site to give vague answers.
So true. I ask a question on the paid support plan and I got an answer copied from a blog I already googled. After several back and forth and escalations, I keep getting the same unhelpful answers and gave up.
Welcome to 2013. To be successful you need to address an immensely huge audience. It is just not physically possible to provide everyone with the kind of customer support you got back when you bought meat from the person who had killed the pig.
We did. And we were paying enough (6 digit monthly bill, not huge but significant I would think) that we did get some nice treatment, although we were definitely not a big enough customer apparently. We adopted a lot of things right away when it came out (ie windows instances, elb). I think that was a mistake and lead to a lot of issues that resulted in responses acting like its not a problem until 6 months later when a fix came out. EC2 was a lot better then my experiences with Terremark though, but we were definitely pennies to them.
What would be really nice to see would be tools to make it easy to migrate between these cloud platforms. The nice thing about making an old-school apache-served website is that you know if your host does wrong by you, you can just move. In many cases, the moving process is simply ordering service, uploading your files, and pointing your domain to the new host.
I realize that this is mainly just the difference between newer technology and decades of standardization, but until cloud providers reach that point, the prospect of bad/missing support is really frightening.
That could all be abstracted away, though, given a PaaS middleman like Heroku. You pay the PaaS piper; they worry about the headache of dealing with Google billing.
I'm pretty sure that most people who have used any of Google's pay for services knows just how bad that support can be.
What happens if something goes wrong with your billing on EC2? No problem, you call them up and sort it out.
What happens if something goes wrong with your billing on any Google product? You'll be down for days while attempting to get Google to even acknowledge a problem.
Until Google fixes their support issues, anybody using a Google service for anything business critical needs to be very careful in weighing up pros and cons.