My biggest complaint about AWS is still EBS and having to guess about for the right provisioned IOPS. Throw in confusing extras like EBS optimized instances, enhanced networking. GCE just abstracts away all these details.
GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
31–40 of 179 posts
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#32Looking forward to the day Google Cloud provides on-demand GPU-backed machines. Currently AWS is the only game in town for that, as far as I know.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#33We moved back and forth between AWS and GCE (based on who gave us free credits). Once we ran out, we chose GCE and never regretted it. GCE 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 assig…
> We're running on average around 25k servers a day
25k number of servers or its the cost of the servers ?
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#34We moved back and forth between AWS and GCE (based on who gave us free credits). Once we ran out, we chose GCE and never regretted it. GCE 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 assig…
> We're running on average around 25k servers a day 25k number of servers or its the cost of the servers ?
Number of servers
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#35Looking forward to the day Google Cloud provides on-demand GPU-backed machines. Currently AWS is the only game in town for that, as far as I know.
Coming early 2017: https://cloud.google.com/gpu/
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#36Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#37Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#38I have serious trust issues with Google. Their history of discontinuing services, dismal support (even for a paid service), and neglect of bugs in SDKs/APIs - all three of which I have experienced first-hand - has left a long-term bitter taste. No doubt some individuals are fantastic, but the organisation as a whole gives me an enduring impression of being systematically arrogant and aloof.
AWS by contrast have demonstrated fanatically helpful support (even on business level, the cheapest), fixing issues within days of reporting, and a willingness to maintain obsolete/deprecated services (like SimpleDB) long after I'm sure they'd wish everyone had migrated away.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#39Looking forward to the day Google Cloud provides on-demand GPU-backed machines. Currently AWS is the only game in town for that, as far as I know.
Apparently, it's coming soon to GCP.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#40We moved back and forth between AWS and GCE (based on who gave us free credits). Once we ran out, we chose GCE and never regretted it. GCE 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 assig…
Sounds like there's a lot of money in DMCA take downs.