3 ms·
This is a bit confusing. I don't suspect Netflix is built using primarily node.js, and I don't see how the Netflix Prize (algorithm for predicting what a person
by lappa 11y ago
This is a bit confusing. I don't suspect Netflix is built using primarily node.js, and I don't see how the Netflix Prize (algorithm for predicting what a person is most likely to want to watch) falls under "scaling".
- johansch 11y agoThis is nitpicking.
- lappa 11y agoAmong the things I had knowledge of, a lot seemed incorrect, so I wasn't quite sure how to take the things I didn't have knowledge of.
- such_a_casual 11y agoHonestly, there are enough problems with the article to warrant a critique. However, someone may not want to take the time to outline every single one. It's incredibly confusing to the reader that the article states Netflix relies on frameworks for one language, and then states that all of their code is written in another language.
- mxpxrocks10 11y agoHey, we got this fixed up on the original post- waiting for Todd to fix the repost on HighScalability shortly. If there are some more problems let us know. We want it to be accurate. http://www.scalescale.com/the-stack-behind-netflix-scaling/ http://www.scalescale.com/the-stack-behind-netflix-scaling/
- mxpxrocks10 11y agohey, thanks for the feedback lappa. We've updated the original article to display node.js better and added a comment. The idea behind mentioning the Netflix prize is to show the openness and willingness to get a lift on their existing recommendation algorithm. There was a 10+% lift in accuracy. Their ability to open up the data and implement really gives them a competitive edge IMHO. It's a shame there seems to be some regulatory reasons they don't do it any more.