by Elgrande » 24 Nov 2013, 21:18
Following my first post, I found this on the Wikipedia page on Netflix.
Netflix API[edit]On October 1, 2008, Netflix launched an application programming interface (API).[245] The Netflix API[246] allows access to data for all Netflix titles as well as access on a user's behalf to manage their movie queue. The API is free and allows commercial use.[247] The Developer Network includes a forum for asking and answering questions. A variety of services have been created around the Netflix API or have integrated the API. Examples include Rotten Tomatoes and The New York Times, which allow users to click to add titles to their Netflix queue or begin watching on Watch Instantly from their pages,[248] and Jinni, which additionally enables search within Watch Instantly and import of some user information like reviews.[249]
The API has allowed many developers to release Netflix applications for mobile devices. On November 16, 2009 Netflix released an official Nokia app that allows some trailer streaming.[250] An official iPhone app was released on August 26, 2010.[128] In June 2012, Netflix announced that it would be cutting back the availability of its public API.[251]
IT infrastructure[edit]In 2010, Netflix migrated its infrastructure to Amazon EC2. Master copies of digital films from movie studios are stored on Amazon S3, and each film is encoded into over 50 different versions based on video resolution, audio quality using machines on the cloud. In total, Netflix has over 1 petabyte of data stored on Amazon, and the data are sent to content delivery networks (including Akamai, Limelight, and Level 3) that feed the content to local ISPs. Netflix uses a number of pieces of open-source software in its backend, including FreeBSD and nginx,[252] Java, MySQL, Gluster, Apache Tomcat, Hive, Chukwa, Cassandra, and Hadoop.[253]
Open source[edit]Netflix has made available as open source many of its internally developed infrastructure management products starting January 11, 2012.[254][255] This includes facilities for automatically scaling a service's hardware footprint and resources, as well as monitoring and maintaining the resiliency of all the supporting infrastructure through the Netflix Simian Army.
Seems to me that it could easily be implemented on a FW although I'm not a programmer.
ayp