News for hackers. Stuff that matters.
Re:Netflix Architect on High Availability and Lessons Learne... by tortilla on Sunday February 09, 2014 @11:24AM (#7205934)
I love their github page:

http://netflix.github.io/

Re:Netflix Architect on High Availability and Lessons Learne... by nikhilkmenon on Sunday February 09, 2014 @12:34PM (#7206215)
Very creative github page. The apps named like movie titles and the UI looks like their Netflix movie browser.
Re:Netflix Architect on High Availability and Lessons Learne... by sync on Sunday February 09, 2014 @12:47PM (#7206262)

    The old Netflix DVD shipping service still runs on the old code base on top of a few large Oracle databases.
Interestingly put. I didn't realize their DVD service is so neglected -- wonder how long it will be around?
Re:Netflix Architect on High Availability and Lessons Learne... by incision on Sunday February 09, 2014 @01:17PM (#7206393)
Is it actually "neglected" if the existing service works reliably under a continually decreasing load [0]?

Surely the actual time in transit makes up the overwhelming majority of time of DVD service and mail is generally a once per day delivery.

Not much point in optimizing what isn't broken in the electronic portion of that operation.

0: http://gigaom.com/2013/10/21/when-will-netflix-kill-its-dvd-...

Re:Netflix Architect on High Availability and Lessons Learne... by jlgaddis on Sunday February 09, 2014 @11:40PM (#7209164)
From another point of view, one could say it's already been fine-tuned and is running quite well as is. In that case, why bother messing with it?
Re:Netflix Architect on High Availability and Lessons Learne... by jamesaguilar on Monday February 10, 2014 @12:06AM (#7209255)
On some level, this is the profitability dream. Engineer something that doesn't cost a lot to run, doesn't need to be changed, and makes a ton of money. Engineers don't like to hear it, because it means less demand for our services, but it's what's best for business.

You can't always drive increased revenue through increased R&D. At this point, substantially everyone who wants a DVD delivery service uses Netflix. As long as someone doesn't come out with a service that makes it significantly easier to rent DVDs over the internet, and as long as attrition caused by the software is very low, any more money spent on Netflix's DVD service is throwing bad money after good.

Re:Netflix Architect on High Availability and Lessons Learne... by tzakrajs on Sunday February 09, 2014 @01:04PM (#7206341)
Re:Netflix Architect on High Availability and Lessons Learne... by akbar501 on Sunday February 09, 2014 @11:42PM (#7209180)
I guess it's a good time to be in Battery's portfolio. Adrian is absolutely brilliant.

Also, that's a big loss for Netflix. I'm sure they have a lot of smart people, but losing someone of Andrian's caliber is not something that can be easily replaced.

Re:Netflix Architect on High Availability and Lessons Learne... by jebblue on Sunday February 09, 2014 @02:46PM (#7206827)
Their Rxjava looks interesting. Too bad us Ubuntu Desktop Linux users with paid Netflix accounts can't watch our movies in Google Chrome yet Crackle movies play just fine. MGo movies too. Odd.
Re:Netflix Architect on High Availability and Lessons Learne... by guiomie on Sunday February 09, 2014 @04:19PM (#7207296)
Anyone familiar with how netflix sorts and delivers their poster repository ? Their OSS stuff on github has nothing for that.
Re:Netflix Architect on High Availability and Lessons Learne... by aruggirello on Sunday February 09, 2014 @02:41PM (#7206788)
Talking about High Availability... the site was horribly slow to load.
Re:Netflix Architect on High Availability and Lessons Learne... by conorgil145 on Sunday February 09, 2014 @04:03PM (#7207216)
The interview is hosted on infoq.com and Adrian (the one being interviewed) is discussing Netflix's architecture. Not really related, though a bit ironic I suppose...
Re:Netflix Architect on High Availability and Lessons Learne... by niio on Sunday February 09, 2014 @11:28PM (#7209118)