Google Cloud vs. AWS Onboarding Comparison
221–230 of 394 posts
Re: Google Cloud vs. AWS Onboarding Comparison
#222Earlier quoted context omitted.
(I work at AWS) > I still, frankly, trust Google's Security more than Amazon's If you have the time, could you expand on this? While I'm not directly involved in security at AWS, I'd be down to forward your thoughts to people who do.
I used to work at Google on Cloud, and am now an AWS customer. Have used both clouds extensively. My comments are mostly backed up by my experience at startups and are not colored by my experience at Google (too different a beast). GCP is great for teams that are also using GSuite because you can set permissions at the level of a Google Group and have them propagate to individual members. You can, of course, also cre…
I’m sure they exist, but over the last dozen or so years I’ve worked with public cloud offerings across 5 or 6 industries and domains, I haven’t found a use case that can’t be easily implemented in the simpler GCP model.
AWS support is really nice. That I miss.
Re: Google Cloud vs. AWS Onboarding Comparison
#223GCP‘s primary target and starting point is enterprise.
OP‘s experience is no surprise.
Re: Google Cloud vs. AWS Onboarding Comparison
#224I've used GCP to great success (with some speedbumps) at 3 companies I've worked for (small and large) over the last 5-6 years. I have a lot of learnings from the experiences to pass on, and one of the key ones is this: work with a reseller. If you've lurked on HN over the past decade you'll have seen tons of stories about how bad Google's customer support is. I don't think GCP's support is anywhere near as terrible…
This feels like working really hard to solve a problem that isn't yours. Why not just get your services from a company that will support you? Why is GCP worth doing this for?
Re: Google Cloud vs. AWS Onboarding Comparison
#225Earlier quoted context omitted.
I mentioned this a couple of times, but Google's CS is non-existent. That's #1 issue holding me back from trying any of GCP offerings.
You need to see GCP as its own brand with its own support team and policies (though they are impacted by some shared technical infrastructure and associated policies). I cannot say whether these are good or bad, only that they are distinct for GCP. Experiences with support or lack of support concerning other Google product areas and divisions, especially those not designed for businesses really don't apply if you kno…
It is true there are individuals that shine, but across the board, Google sucks at support. It starts at the top with what kind of company they want to be, and goes from there.
They do not like humans.
Re: Google Cloud vs. AWS Onboarding Comparison
#226Google's business model is to have no customer service and have customers discard-able without notice when Google chooses. Why would a business want to do business to business with Google and actually pay them at this point? They do 'free' sort of well but they are a terrible option for dependable partner whether you pay them or not.
From GCP docs [0]: Effect of ToS violations Google-wide disabled account In some cases a Google-wide account (which covers access to a variety of Google products like Google Photos, Google Play, Google Drive, and GCP) will be disabled for violations of a Google ToS, egregious policy violations, or as required by law. Owners of disabled Google accounts will not be able to access their Google Cloud resources until the…
When even Google themselves is recommending gaming their system since they can't guarantee it won't screw you over, that should be a warning sign.
Re: Google Cloud vs. AWS Onboarding Comparison
#227Earlier quoted context omitted.
Surely product makes these decisions, not engineers, right? I agree that customer empathy is important, but I don't think we can conclude that the engineering team (rather than the product team) is the source of the deficiency?
> Surely product makes these decisions, not engineers, right? I agree that customer empathy is important, but I don't think we can conclude that the engineering team (rather than the product team) is the source of the deficiency? I haven't worked inside AWS or GCP, but I've never seen product get everything they want, especially around maintenance/downtime. If "less downtime" is on the roadmap but engineering is cons…
It probably is hard and intensive. Engineering shouldn't lie and promise that it will be easier. Product has to take that engineering estimate and determine whether to work uptime or some sexy feature (and sexy features usually win because of perverse incentives).
Moreover, I have a hard time believing this for a couple reasons: first of all, I've scarcely met engineers who were opposed to improving product reliability, maintainability, etc. The portrait of Google engineers arguing that database services fundamentally shouldn't be HA (and customers are "using it wrong" for wanting HA DBs) is particularly incredulous. Secondly, I've never heard of an organization where engineering held political power over product decisions, but I have worked in several places where product dictated engineering solutions. Businesses trust product more readily than engineering because the things that engineering is always petitioning for are abstract and "costly" (deferring some immediate profit for reduced costs in the long run) while the things product wants are usually tangible and profitable.
Re: Google Cloud vs. AWS Onboarding Comparison
#228On AWS: fast, close to our needs and all setup in days. After our one year program cam to an end we still had around 50k in credits. One email asking if they could extend for one or two months, they extended for 6. We also messed up the last month as we did not setup any limits and spend more than 17k in cloud computing - they offered us an 80% discount!
On GCP: We got accepted very fast (2 days). But we struggled for 2 months to get GPU quota. The communication is not fluid and we were pointed from sales rep to support to sales rep.
Also from the management perspective (but this is purely my opinion), GCP is a labyrinth. You need a phd in GCP to setup your users with permissions. And i still could not figure out how to create good usage reports out of it.
Re: Google Cloud vs. AWS Onboarding Comparison
#229Earlier quoted context omitted.
One thing that GCP is far better at is account setup. Having everything nested under a single gsuite organization with folders and projects and IAM flowing through is incredibly easy to work with and makes permissions simpler to understand. AWS has a long ways to go in this regard.
I came from an AWS background to my current company's GCP setup and was very confused at how IAM worked on GCP for a long time. Now that I know the system, though, I agree with you. It really makes a ton of sense and works really well. The biggest problem I have with GCP is that something will say "you need the foo.bar.baz permission", and when I go to the IAM page to give that to myself... there is nothing in the se…
Re: Google Cloud vs. AWS Onboarding Comparison
#230Where is Azure here?