3 ms·

Downside is that GCP still has the same faults regardless of which CPU is being used. Things like poor customer interaction, things not working as designed etc.

Downside is that GCP still has the same faults regardless of which CPU is being used. Things like poor customer interaction, things not working as designed etc. Switching to ARM won't solve that.

CuriouslyC 3y ago
As much as I don't trust google and their customer service is trash, their infrastructure is mostly good and some of their services are very aggressively priced. I wouldn't 100% buy into GPC but a multi cloud solution that leverages some of the good bits is definitely a top tier approach.
- hnav 3y ago
  how do you deal with egress costs?
  - CuriouslyC 3y ago
    I don't think they're a big deal if you're hitting vertex for inference and cloud run for long tail services. If you're 50/50 with AWS though that might be a different story.
thebytefairy 3y ago
In what ways? In my experience I've found GCP to easiest to use
- redman25 3y ago
  Feels like they've changed their pricing structure for bigquery multiple times in the past couple years. They've never turned the status page yellow or red but there have been a few incidences where from our perspective the service was clearly degraded.
- gigatexal 3y ago
  yeah on the whole (data eng by day -- data eng contractor by night) using both AWS and GCP I much prefer GCP to AWS. I find it far more simple to use, has sane defaults, a UI that isn't harmful to users doing clickops, etc. AWS gives you low level primitives to build the moon or shoot yourself in the foot.
- shrubble 3y ago
  It's not about easiest to use but the way in which problems are handled. I am aware of case where something failed after being assured it would work by GCP ... when they got someone a GCP tech lead on the video call he started by saying it was all 'best effort' and that it might take several days to resolve. Ultimately it was fixed in 8 hours but that sort of laissez-faire attitude has led to the company in question making plans to go elsewhere.

Downside is that GCP still has the same faults regardless of which CPU is being used. Things like poor customer interaction, things not working as designed etc. Switching to ARM won't solve that.

CuriouslyC 3y ago

As much as I don't trust google and their customer service is trash, their infrastructure is mostly good and some of their services are very aggressively priced. I wouldn't 100% buy into GPC but a multi cloud solution that leverages some of the good bits is definitely a top tier approach.

hnav 3y ago
how do you deal with egress costs?
- CuriouslyC 3y ago
  I don't think they're a big deal if you're hitting vertex for inference and cloud run for long tail services. If you're 50/50 with AWS though that might be a different story.

thebytefairy 3y ago

In what ways? In my experience I've found GCP to easiest to use

redman25 3y ago
Feels like they've changed their pricing structure for bigquery multiple times in the past couple years. They've never turned the status page yellow or red but there have been a few incidences where from our perspective the service was clearly degraded.
gigatexal 3y ago
yeah on the whole (data eng by day -- data eng contractor by night) using both AWS and GCP I much prefer GCP to AWS. I find it far more simple to use, has sane defaults, a UI that isn't harmful to users doing clickops, etc. AWS gives you low level primitives to build the moon or shoot yourself in the foot.
shrubble 3y ago
It's not about easiest to use but the way in which problems are handled. I am aware of case where something failed after being assured it would work by GCP ... when they got someone a GCP tech lead on the video call he started by saying it was all 'best effort' and that it might take several days to resolve. Ultimately it was fixed in 8 hours but that sort of laissez-faire attitude has led to the company in question making plans to go elsewhere.