Netflix Launches Its Own Content Delivery Network
1sockchuck writes "Netflix has launched its own content delivery network to manage data delivery for its streaming video service. ISPs can choose to host caching appliances in their data centers, or peer with Netflix at Internet Exchanges. 'Netflix will provide either form of access at no cost to the ISP,' it said. As part of Open Connect, Netflix is sharing its hardware appliance design and the open source software components of the server. Does this mean Armageddon for the CDNs currently serving Akamai? Not really, according to analysts, citing the leverage Netflix had in dealing with providers."
will their new CDN work out that I'm not in the US more effectively?
So Comcast is going to roll over for this? Comcast is an integrated Cable TV/ISP, which wants to favor their own delivery mechanism and content relationships. Only Common Carrier status for Internet delivery will break that stranglehold - lots of luck for achieving that in the USA!
- Leonard
Less buffering, more buffering? Will the Wii app still suck? Will their website still suck? Will all Android Netflix apps still app still suck?
I think the real story here (which the summary completely missed) is that Netflix is not just setting up caching mirrors, they are trying to get the competitors to host the caching servers! Most ISP's in the US (which is about the only place netflix works anyways) are the same companies that have been trying to destroy netflix to save their cable-TV interests.
Now they just need some content to deliver.
Seriously, The Cablecos and Telcos won't probably even bother. In an *ideal* world, they would do it to save bandwidth (and therefore not charge their costumers for that bandwidth), but I really doubt Videotron, Rogers, Bell and all the other money-hungry monopolistic providers will do it. It would eat into their Rape-the-customer-tv business. Besides, since we can get about third-world country 50GB/month of bandwidth here in Quebec, how many hours of Netflix does that give me?
Those big ISPs already have a bunch of cdn servers (Akaimai comes to mind), but they still count their usage towards your monthly cap, even if it doesn't cost them a penny on their peer links (since the content is already mostly cached).
I've got better things to do tonight than die.
Big CDNs don't make much money on Netflix - the margiins in media delivery suck and Netflix is notoriously cheap. CDNs might not mind losing some bad paying traffic so they can fill their networks with stuff they get more money for serving.
If the CDNs want to stop serving Netflix traffic so they are free to serve up other, more lucrative traffic, couldn't they already do that by charging Netflix more money, which would either give the CDN more revenue, or get Netflix off their network, so they win either way? Why would they want to see Netflix create an open source CDN appliance that Netflix (and others) can use to replace the CDNs?
Apparently the answer is now YES! Keep in mind that keeping your CDN server updated will generate a steady inflow of 80-100 Mbps* *This is the actual number that was given to a WISP operator by a Netflix agent, as reported on dslreports.com many months ago. Sorry, I went looking but wasn't able to dig up the old thread. I'm sure that number has only grown in the intervening months.
I am literally 3000 tokens away from the chaotic crossbow --Stephen
All these posts and no-one has mentioned it runs on FreeBSD?
Netflix's New Peering Appliance Uses FreeBSD
Given that they are using FreeBSD on their new CDN (and most of their new back-end infrastructure), why do you think it would make Linux support more likely?
I am TheRaven on Soylent News
BSD is dying trolls are dying too.
If they keep with the Queue concept, I'd like to see multiple queues. So I can set one up for shows my kids like to see and one for shows I like watching. This way, I don't need to scroll through Bob the Builder Live and Yo Gabba Gabba to find my shows.
My sci-fi novel, Ghost Thief, is now available from Amazon.com.