Paper: Netflix’s Transition to High-Availability Storage Systems
highscalability.com
highscalability.com
I'm starting to suspect big customers get a discount in exchange for adding their name on the dotted line of these PR Lorem Ipsum's.
They (you?) switched from an expensive platform to another expensive platform. In an article about a transition I hope to find hard data about the performance- and cost-tradeoffs that were made.
How many hosts, how much data, how much traffic, how many queries, how much latency, how many dollars?
Instead I got a generic "AWS is awesome" boilerplate along with a generic AWS best-practice bullet-list...
FWIW, here's a not-so-old chart from backblaze about relative storage cost: http://blog.backblaze.com/wp-content/uploads/2009/08/cost-of...
S3 ranges way up there and knowing that figure first-hand (and also their traffic rate) I sort of expected cost considerations to be at least mentioned in a document titled "XXX transition to ... storage-system".
If you consider that a home-rolled solution is not elastic to demand and therefore I'd probably wind up with a capacity factor < 50%, it's a wash pricewise. Meanwhile, I know the AMZN-based system is going to make me sleep easy when it comes to business continuity nightmares.
blog post: http://irr.posterous.com/netflixs-transition-to-high-availab...
direct download link: http://s3.amazonaws.com/files.posterous.com/irr/1OaUyyUq9eF2...