Hacker News new | past | comments | ask | show | jobs | submit login

Developer experience on GCP is vastly superior to AWS.

- Pricing on GCP is much easier, no need to purchase reserved instances, figure out all the details and buried AWS billing rules. Run your GCP instances and automatically get discounts. AWS reserved instances requires knowing your instance types, knowing that you can purchase the smallest type of an instance class and combine, knowing that you can only purchase 20 reserved instances per zone/per region in an account. So many gotchas.

- GCP projects by default span all regions. It is much easier if you run multiple regions, all services can communicate with all regions. Multi-region in AWS is sort of a nightmare, setting up VPC peering, can't reference security groups across regions, etc..

- Custom machine types. With GCE, you simply select the number of cores you need and memory. No trying to decipher the crazy amount of AWS instance types T2, T3, M5, M5a, R5, R5a, C5, C5n, I3...

- Instance attached block storage is easier to grok and in my experience is much faster than EBS. The bigger the disk on GCE, the more IOPS. No provisioned IOPS madness.




Another great point to GCP: -- You can setup an 'organization' that will hold multiple projects, in a hierarchy of folders. You can set permissions/roles on a folder, and have them propagate down to all projects underneath.


> no need to purchase reserved instances

GCE offered committed use discounts for quite some time (note: completely different from sustained use discount that is automatic), by ignoring this discount tier, the results from this post look significantly worse

The idea that "developer experience" is paramount is the entire reason why there is an entire sub-industry of vendors dedicated to cost optimization, following in the wake of choices made with completely the wrong business priorities in mind


AWS has cheaper discounted instances though too.


I'd argue that developer experience on AWS is better. I work on both. Two things stand out for me:

Serverless lambdas on AWS are more functional. Google does not have comparable functionality yet.

Auth and IAM permissions are far more configurable on AWS. Google's ACL does not have the same depth of tools there. Making the ACL do the same thing as AWS's IAM generally feels cludgy and a pain.

Working with AWS there is a deep ecosystem of tools there and I only use maybe 30%. Working with Google, there often are tools and logging missing that I took for granted in AWS.


What feature do lambdas have that cloud functions don't? (asking not challenging)

Never used lambdas but the fact that gcloud functions allow python imports make them pretty versatile from what I can tell


> The bigger the disk on GCE, the more IOPS

This is true on AWS, too. Common advice for AWS is to just make your disk bigger instead of paying for provisioned IOPS.


Yet more reasons my employer chose to partner with GCP instead of AWS

On the "enterprise" end of cloud computing, the only truly good options are GCP & Azure

AWS is very much the IBM of yesteryear - it's expensive, but "no one ever got fired for buying AWS" ... except AWS is about to have (even starting already) their own IBM moment - question is, will they fail to pivot the way IBM did?


Local SSDs can also be attached to any instance types.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: