5 ms·

- Native integration with G-Suite as an identity provider. Unified permissions modeling from the IDP, to work apps like email/Drive, to cloud resources, all the

• scarface74 8y ago
  Your response is from a geek’s viewpoint. No insult, intended, I’m first and foremost a 30 year computer geek myself - started programming in 65C02 assembly in 6th grade and still mostly hands on. But, whether it is right or not, as an architect/manager, etc, you have to think about what’s not just best technically. You also have to manage your reputational risks if things go south and less selfishly, how quickly can you find someone with the relevant experience. From a reputation standpoint, even if AWS and GCP have the same reliability, no one will blame you if AWS goes down if you followed best practices. If a global outage of an AWS resource went down, you’re in the same boat as a ton of other people. If everyone else was up and running fine but you weren’t because you were on the distant third cloud provider, you don’t have as much coverage. I went out on a limb and chose Hashicorp’s Nomad as the basis of a make or break my job project I was the Dev lead/architect for hoping like hell things didn’t go south and the first thing people were going to ask me is why I chose it. No one had heard of Nomad but I needed a “distributed cron” type system that could run anything and it was on prem. It was the right decision but I took a chance. From a staffing standpoint, you can throw a brick and hit someone who at least thinks they know something about AWS or Azure GCP, not so much. It’s not about which company is technically better, but I didn’t want to ignore your technical arguments... Native integration with G-Suite as an identity provider. Unified permissions modeling from the IDP, to work apps like email/Drive, to cloud resources, all the way into Kubernetes IAM. You can also do this with AWS - use a third party identity provider and map them to native IAM user and roles. https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp.html https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_cr... Cost. Apples to apples, GCP is cheaper than any other cloud platform. Combine that with easy-to-use models like preemptible instances which can reduce costs further; deploying a similar strategy to AWS takes substantially more engineering effort. The equivalent would be spot instances on AWS. From what (little) I know about preemptible instances, it seems kind of random when they get reassigned but Google tries to be fair about it. The analagous thing on AWS would be spot instances where you set the amount you want to pay. Class leading software talent. Google is proven to be on the forefront of new CS research, then pivoting that into products that software companies depend on; you can look all the way back to BigQuery, their AI work, or more recently in Spanner or Kubernetes. All of the cloud providers have managed Kubernetes. As far as BigQuery. The equivalent would be Redshift. https://blog.panoply.io/a-full-comparison-of-redshift-and-bigquery https://blog.panoply.io/a-full-comparison-of-redshift-and-bi... Reliability is just one factor in the equation, and GCP definitely isn't that far behind AWS Things happen. I never made an argument about reliability.
  • maktouch 8y ago
    > The equivalent would be spot instances on AWS. They're equivalent in the sense that you have nodes that can die anytime, but it's much more complicated. You could technically have a much lower cost on AWS by aggressively bidding low but we've had a few instances where the node only lived a few minutes. Preemptibles nodes are max 24h, and from our stats, they really live around that amount of time. I think the lowest we've had was a node dying after 22h. You also save out of the box because they apply discount when your instance is running for a certain number of hours. You can even have more discount by agreeing to a committed use which you pay per month instead of one-shot unlike AWS. I'm going to add a few more reasons to the above reply: - UI and CLI is so much better in GCP I don't have to switch between 20 regions to see my instances/resources. From one screen, I can see them all and filter however I like. - GCP encourage creating different projects and apply same billing. It's doable in AWS too, of course, but coupled with the fact that you have different projects and regions, and you can't see all instances of a project at once, this makes a super bad experience - Networks are so much better in GCP Out of the box, your regions are connected and have their own CIDR. Doing that in AWS is complicated. - BigQuery integration is really good A lot of logs and analytics can be exported to BigQuery, such as billings, or storage access. Coupled with Data Studio and you have non technical people doing dashboards. - Kubernetes inside GCP is a lot better than AWS' https://blog.hasura.io/gke-vs-aks-vs-eks-411f080640dc https://blog.hasura.io/gke-vs-aks-vs-eks-411f080640dc - Firewall rules > EC2 Security Group - A lot of small quality of life that makes the experience a lot better overall ... like automatically managing SSH keys for instances, instead of having a master ssh key and sharing that. Here's the thing though, a lot of GCP can be replicated, just like what you linked for the identity provider. With GCP, there's a lot of stuff out of the box -- so dev and ops can focus on the important stuff. Overall, AWS is just a confusing mess and offers a very bad UX. Moving to GCP was the best move we've made.
    • halbritt 8y ago
      Not much to add here other than this reflects my experience as well. Moved for bizdev reasons, and really appreciated the improved quality of life.
  • 8y ago
• majewsky 8y ago
  > If you're on Kubernetes and its not on GKE, then you've got legacy reasons for being where you're at. Or you have legitimate reasons for running on your own hardware, e.g. compliance or locality (I work at SAP's internal cloud and we have way more regions than the hyperscalers because our customers want to have their data stay in their own country).
  • 013a 8y ago
    That's totally fair; that comment was just in reference to comparing other cloud providers (AWS and Azure primarily)