3 ms·

Which aligns with the primary difference between Google and Amazon, customer service. Amazon is as good at service as Google is bad. If my memory serves me corr

Which aligns with the primary difference between Google and Amazon, customer service. Amazon is as good at service as Google is bad. If my memory serves me correct, Google had outsourced at least some of the GCP customer service to HP.

YetAnotherNick 3y ago
Customer service isn't wildly different between GCP and AWS. I think it's the finish of the product. AWS has far more finished product and even for smaller services it mostly works as intended. While GCP it is very hit or miss. I have seen so many edge cases in smaller GCP services like composer, old ML platform, dataflow etc. While GCP is definitely more intuitive. You don't need to create 2 different IAM profile for anything you want to solve. So GCP feels more like Digital Ocean + bunch of services with varying quality.
- zgluck 3y ago
  GCP has a smaller number of services but they tend to be very well designed with excellent taste. AWS has a bazillion services, often very obviously designed by people without good taste and/or experience. GCP's incompleteness is super annoying. The general daftness of AWS service design is tiring and somewhat soul-sucking. I used to think that Google would eventually get there, but lately I've realized that they are totally happy offering an 80% product forever. So for now I'm very reluctantly team AWS.
  - YetAnotherNick 3y ago
    > GCP has a smaller number of services but they tend to be very well designed with excellent taste. I would have said the same before using GCP. At first everything goes super smoothly and the experience is definitely better than AWS. Then you start seeing undocumented behaviour again and again. In comparison, it is much rarer to get any undocumented behavior in AWS.
    - zgluck 3y ago
      Not my experience. They tend to work well. The problems comes when you want to do something very slightly unusual.
      - YetAnotherNick 3y ago
        > The problems comes when you want to do something very slightly unusual. That's exactly what I said. Main services are more or less stable, but there are edge cases in smaller services if you want to do something unusual.
    - goalonetwo 3y ago
      Fully agree with this. I have used GKE at scale as an example. It starts to break down significantly once your cluster reaches a couple hundred nodes. Only way to solve it is to have support resize your controller nodes manually. And as support for anything google is horrible, that task takes multiple hours.

YetAnotherNick 3y ago

Customer service isn't wildly different between GCP and AWS. I think it's the finish of the product. AWS has far more finished product and even for smaller services it mostly works as intended. While GCP it is very hit or miss. I have seen so many edge cases in smaller GCP services like composer, old ML platform, dataflow etc. While GCP is definitely more intuitive. You don't need to create 2 different IAM profile for anything you want to solve. So GCP feels more like Digital Ocean + bunch of services with varying quality.

zgluck 3y ago
GCP has a smaller number of services but they tend to be very well designed with excellent taste. AWS has a bazillion services, often very obviously designed by people without good taste and/or experience. GCP's incompleteness is super annoying. The general daftness of AWS service design is tiring and somewhat soul-sucking. I used to think that Google would eventually get there, but lately I've realized that they are totally happy offering an 80% product forever. So for now I'm very reluctantly team AWS.
- YetAnotherNick 3y ago
  > GCP has a smaller number of services but they tend to be very well designed with excellent taste. I would have said the same before using GCP. At first everything goes super smoothly and the experience is definitely better than AWS. Then you start seeing undocumented behaviour again and again. In comparison, it is much rarer to get any undocumented behavior in AWS.
  - zgluck 3y ago
    Not my experience. They tend to work well. The problems comes when you want to do something very slightly unusual.
    - YetAnotherNick 3y ago
      > The problems comes when you want to do something very slightly unusual. That's exactly what I said. Main services are more or less stable, but there are edge cases in smaller services if you want to do something unusual.
  - goalonetwo 3y ago
    Fully agree with this. I have used GKE at scale as an example. It starts to break down significantly once your cluster reaches a couple hundred nodes. Only way to solve it is to have support resize your controller nodes manually. And as support for anything google is horrible, that task takes multiple hours.