News for hackers. Stuff that matters.
Re:GCE vs. AWS: Why You Should Never Use Amazon by xref on Tuesday July 05, 2016 @02:43PM (#12038603)
In all the AWS workloads I've dealt with none was ever suited to spot instances
Re:GCE vs. AWS: Why You Should Never Use Amazon by boulos on Tuesday July 05, 2016 @07:05PM (#12040155)
Huh. Do you not use say EMR? We've got lots of folks running Hadoop/Spark either directly or through Dataproc (https://cloud.google.com/dataproc/).

All of our Monte Carlo finance customers as well as the genomics folks at the Broad Institute seem pretty happy.

If you're saying they're a bad fit for stateful applications like databases and web backends, I agree ;).

Re:GCE vs. AWS: Why You Should Never Use Amazon by mattkrea on Tuesday July 05, 2016 @04:42PM (#12039406)
We run a bunch of production workloads on them. Just look at the spot pricing history in US-East-1A and 1B for a good idea at the stability.

This is over a year now and only once did I have any sort of interruption and even there it was in only one AZ so of course I had other instances up and able to take the load.

Re:GCE vs. AWS: Why You Should Never Use Amazon by hagbarddenstore on Wednesday July 06, 2016 @04:59AM (#12041973)
You do know that AWS AZs are different per customer? Your us-east-1a isn't the same as my us-east-1a.
Re:GCE vs. AWS: Why You Should Never Use Amazon by blackoil on Tuesday July 05, 2016 @10:01PM (#12040788)
All the test infrastructure can easily go on test if you have auto-scaling. Some percentage of production, you can move to Spot.