News for hackers. Stuff that matters.
Re:GCE vs. AWS in 2016: Why You Shouldn't Use Amazon by gdgtfiend on Monday December 26, 2016 @05:45PM (#13260181)
Two points here really hit home with me about AWS (not in comparison to GCE though since I've never tried it).

1) Reserved Instances: I think the pricing model for this has become very outdated since the beginning of AWS, and it is definitely becoming cumbersome (and therefore scary) to use.

2) ELB + Traffic Spikes: I have tried (unsuccessfully) to pre-scale an ELB to prepare it for the traffic it was about to receive. I tried to pre-scale for this project 3 different times, in coordination with support and without them. I could not do it. Very frustrating.

I think these are all signs of extreme growth, and a strange organization of engineering units inside of AWS. However, as OP descried.. we are much to heavily invested in AWS to consider an infrastructure shift at this point

Re:GCE vs. AWS in 2016: Why You Shouldn't Use Amazon by tejasmanohar on Monday December 26, 2016 @06:31PM (#13260332)
We also manually sync up with AWS support to "warm up" our ELBs... I guess they don't expose an option to avoid abuse, but it really does seem like an implementation caveat.
Re:GCE vs. AWS in 2016: Why You Shouldn't Use Amazon by tuananh on Monday December 26, 2016 @10:27PM (#13261103)
Can you talk more about ELB + Traffic Spikes?

Under high traffic, ELB will fail?

How do you pre-scale the ELB?

Many thanks.