Level 3 Comments On The Future Of HTTP Based Streaming
Over on the StreamingMedia.com discussion lists, a big debate has been raging over whether or not HTTP based streaming and services like Smooth Streaming are cheaper for content delivery networks to deploy. Earlier in the week I wrote a post saying that today, it's not cheaper to deploy and for content owners, doesn't cost them any less than other forms of delivery. With both Microsoft and Apple making a strong push for HTTP based streaming and Adobe hinting since the beginning of the year that they will provide support for it before too long, there's no question that HTTP based streaming will play a big
role in the future of video delivery.
While I spoke to a couple of CDNs about their HTTP deployments for both Apple and Microsoft's platforms, Level 3 was willing to give out some additional details for the blog and I did a quick Q&A with Mark Taylor, the Head of Media Product and Strategy at Level 3. Here are his thoughts on HTTP based streaming and some of the positive signs Level 3 is seeing with their deployments.
Question: Is HTTP based streaming cheaper for Level 3 to deploy and manage today when compared to FMS and WMS services?
Yes. There are three areas where it is more cost effective for a CDN.
Firstly, we have no software integration on any of our edge servers with the new HTTP streaming solutions. For significant new versions of proprietary streaming protocols, that do not use HTTP, this integration is a significant amount of work for our development teams. We effectively have to fold the new technology into our own ecosystem. There are a lot of things we have to build to turn the streaming vendor's code, a framework really, into a functional service. And even when we have the code built we have to go through rigorous regression testing before we can roll it out onto the thousands of servers throughout our network – we clearly have to be completely satisfied that no existing customers will be impacted negatively. Contrast that with the new HTTP-based streaming technologies where we need do almost nothing; maybe a few tweaks to our existing caching code in order to improve efficiency. And of course nearly every time there is a new feature or a code upgrade we need to go through the same cycle again.
Secondly, it is simpler and more efficient for our operational teams to manage. There is less complexity and we don't need to build any new management tools. Managing one technology is clearly easier than managing many technologies that all essentially do the same thing.
Thirdly, CDNs do not pay any traffic/bandwidth/volume related fees to the HTTP streaming software vendors.


