Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yes, it is.

"If you’re used to designing and deploying applications in your own data centers, you need to be prepared to unlearn a lot of what you know."

Which is it? Did it save them money because they didn't have to "build their own redundancy and failover" or did they have to build a bunch of custom tools like Chaos Monkey because "I knew to expect higher rates of individual instance failure in AWS, but I hadn’t thought through some of these sorts of implications." ???

From reading Netflix' blog, it's clear that it was a huge learning and engineering effort. That cost has to be taken into account and added to the fact that across many AWS offerings, you're looking at as much as a 10x price / performance penalty versus dedicated or collocation. I'm unconvinced that they couldn't have done it cheaper and better through more transitional approaches, and moreso that it's a meaningful indicator for anyone else.

AWS has been massively innovative. But it's much more expensive, and a huge part of their business is sales and getting CXOs onboard, not necessarily providing good value.



"That cost has to be taken into account and added to the fact that across many AWS offerings, you're looking at as much as a 10x price / performance penalty versus dedicated or collocation."

This.

The pricing is especially egrerious in bandwidth charges which for AWS are almost pure profit.

Amazon is only cheap if you don't use it.


I've heard that the prices are egregious only in bandwidth charges and that other things were not as bad. Does anyone have concrete numbers to compare?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: