Hacker News new | ask | show | jobs
by ewhauser421 2771 days ago
I see a lot of Google Cloud bashing on this thread, so thought I'd share my viewpoint as a customer.

We've been a Google Cloud customer for close to a year now and just recently signed a deal to move all of our infrastructure over to them from AWS. I've previously managed infrastructure spends of $>10M a year on AWS before, so have a decent amount of experience with them. I've never used Azure.

We had been running our CI/CD pipelines on Google mostly because we received startup credits from them. Over time, our use cases expanded as we adopted BigQuery for data warehousing. We choose to commit to Google long term because we've been a heavy Kubernetes shop in got tired of managing it ourselves on Amazon. We participated in the Amazon EKS alpha and felt that they were years behind Google in their Kubernetes implementation. We have probably been able to save 1-2 DevOps hires this year by adopting some of Google's managed services.

If there is a downside on the technical side, it is that some of their products don't have the same number of features as Amazon such a prefix signing and reporting on GCS. There also isn't the same level of community awareness on how to use their stack so documentation gaps are more painful. Other things like a lack of presence in China could be challenging in the future as well.

On the business side, Google has been amazing to work with. Whenever we have a technical question, the sales team has generally been able to quickly get us an answer or we've got to talk to the product PM. When working with Amazon, you are usually referred to a solutions integrator who can't answer tough technical questions. Google is very open with early access releases as long as you're willing to provide them feedback - which they truly value. Their sales processes aren't as mature as that of an established enterprise company - which can be a good or a bad thing - but they've certainly earned our trust as an enterprise customer.

In some ways, any of the big 3 are going to have marks against them in some way as they just do too many things for them not to piss you off in some way. I wasn't a fan of Microsoft a decade ago because they regularly killed open source products I liked by releasing their own version of it under the Microsoft name.

When looking for partner I'm looking for someone who can accelerate my business and earn my trust. So far, that's what I've gotten from this relationship.

5 comments

> Other things like a lack of presence in China could be challenging in the future as well.

Well, to be fair, NONE of the big clouds have any presence in China. They are "in China" in name only.

For instance, 'AWS' China is not AWS, you will be dealing with Sinnet for Beijing or whoever else operates the Ningxia region. The underlying software is a baby version which doesn't have anywhere near the same amount of features. Frankly, the only benefits vs a local cloud provider are that the name is still retained (so you have your bases covered if anyone complains) and the API is AWS compatible.

It is a similar story on the other clouds. So I wouldn't weight this that heavily against Google.

Also, all of this only applies if you have boots on the ground. It's not like one can just create an account in China and run with it. It's an expensive and lengthy process.

Ssh'ing into China AWS boxes is like 300 baud modem days born again. I work across from people trying to setup AWS China infrastructure and the curse words fly with alacrity and frequency.
I’m not sure what you are angling at here.

The China regions might not have all the AWS services present, and they have some extra restrictions, but they aren’t some kind of clones of AWS software.

Unless I’m missing something, they are the same versions of what runs in the other regions.

You can't go into the AWS console and select a region in China and then provision resources.

AWS-China is literally a different organization with a different service on a different URI and with whom you'll need to establish a different contractual relationship.

It's a different 'partition' the same way that govcloud is a different partition. Separate for legal reasons, but the same technology underneath.
Limited versions.

No experience with AWS China, but I taught a class to some folks who used one of the restricted AWS regions and the services and features were limited when compared to normal aws regions, according to the students.

There are laws and regulations in China about who can own the physical infrastructure, but that doesn't mean that it isn't AWS. The implication that the only benefit is that the name is retained is simply false.

Due to laws and logistics, AWS Classic -> AWS China aren't at full feature parity, but it's certainly not some watered down or different version of the AWS cloud.

> Well, to be fair, NONE of the big clouds have any presence in China. They are "in China" in name only.

Azure has a region in China which is not a baby version of its public cloud offering. It might not have some new SaaS products but for core offerings it's exactly the same feature wise.

When working with Amazon, you are usually referred to a solutions integrator who can't answer tough technical questions.

Amazon “Consultants” are basically useless. The ones I’ve had the displeasure of dealing with only know the netops side and the best they can do is help you do a “lift and shift”. They usually know very little about how to implement all of the other managed services AWS offers.

I was the Dev lead at a previous company with no AWS experience and they brought in “consultants” to help us move to AWS. They gave no guidance on how to actually develop a product using AWS services even though I explained in high level my proposed architecture. I could have easily cut the cost by over 60% if I had known all I know about AWS now or the consultants could have actually helped.

Services at this scale fascinates me, can you give any more details on your software stack, and the problems you are facing!?
What's prefix reporting?
$10M spend, doesn't investigate more than 2 options. Nice.
To be clear, we spent $10M+ annually on AWS at a previous company. We do not spend that amount at my current employer.