GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
thehftguy.com
GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
1–10 of 179 posts
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#2Is Google Cloud support even acceptable? Google is known for poor or no support for most services.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#3> AWS Premium Support is mandatory Is Google Cloud support even acceptable? Google is known for poor or no support for most services.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#4Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#5Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#6Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#7GCE has many quirks, for instance the inconsistency between API and the UI, it misses the richness of the services offered by AWS but everything GCE does offer is just faster, more stable and much more consistent.
One of the biggest problems with AWS is that once you outgrow the assigned limits, it becomes a hell to get more resources from them. We're running on average around 25k servers a day, majority of them preemptible (spot). AWS requires that you request exact type and location for your instances. GCE only asks for a region and then overall resources (e.g. number of CPUs).
Also the pricing is much less complicated. 1 core costs y, 32 cores cost 32*y.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#8Also, the AWS premium support fee is negotiable for some customers from what I have heard. They don't like to negotiate down, though!
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#9What reason is AWS premium support mandatory? I ask because I'm currently building out SaaS offering on AWS and haven't yet hit any issues requiring support. Can I expect to start seeing issues as traffic scales up to a certain level?