For those interested it's Amazon's rebuttal to the story discussed here: http://news.ycombinator.com/item?id=3580273
For those interested it's Amazon's rebuttal to the story discussed here: http://news.ycombinator.com/item?id=3580273
My company works in the media space and I love EC2- during the week our loads are low but when it's Superbowl Sunday or the GRAMMYs, the ability to spin up capacity is huge. But the fact that I'm _not_ paying for that capacity 24/7 is even bigger.
Here's why it sucks:
131 x amazon extra large: $56k after Amazon fixed the pricing
- 524 amazon cores
- tons of crap io
- 2tb of ram
131 x bought servers: $61k
- this includes colo and bandwidth and amortized cost of buying
- excludes labor which Amazon makes mention of
131 x $289 leased servers [1]: $37k
- 524 real cores, each with hyperthreading
- tons of dedicated disk io (raid 1 SSD and raid 1 SATA!!)
- 2tb of ram
- server breaks someone fixes it
These dedicated servers are obviously going to shit all over EC2 virtual servers if you're doing anything that involves disk or cpu so you could in all likeliness shave another $10k - $15k off the hosting bill to match the AWS capacity.
[1] https://hivelocity.net/cart/configure/13c6f96e41#50a2e-82f3f
I love some aspects of AWS, but I find it hard to trust them when it comes to the cloud vs. dedicated hosting discussion.