This website uses cookies to ensure you get the best possible experience.

Back

How to Think about eCDN

One of the most feared problems when working with video is bandwidth usage.

Live streaming is unforgiving when it comes to bandwidth demands. The increase in usage is not always accounted for in network infrastructure, which usually predates the company’s newest video project. Actually increasing the internet speed is extremely costly, if it’s even possible.

The symptoms of choking bandwidth start with bad user experience (buffering, mainly) and lead to video service disruptions. In some cases, the excessive usage could cause a total network disruption.

How does eCDN helps address the bandwidth issue?

The first thing you need to know of eCDN is that anything your users try to retrieve from the cloud will only be downloaded once. The first user pulls the content from the Internet and all the following users get it from your eCDN node cache, inside your network.

So in this example, 100 users can join the live event or watch the latest HR video, without overwhelming the 10Mbps internet link.

(Note: 1Mbps used for the simplicity of the example)

OK, but I have many offices and a complex network. Where should I deploy these eCDN nodes?

Simple: anywhere where you can expect a bandwidth bottleneck.

Let’s look at this example with four offices:

  • HQ
    • 100Mbps internet connectivity
    • 100 concurrent users
  • Location 1
    • 2Mbps internet connectivity
    • 100Mbps connectivity to HQ
    • 20 concurrent users
  • Location 2
    • 10Mbps internet connectivity
    • 2Mbps connectivity to HQ
    • 20 concurrent users
  • Location 3
    • 10Mbps internet connectivity
    • 100Mbps connectivity to HQ
    • 5 concurrent users
    • No local IT team or infrastructure

In all offices except one, there is not sufficient internet connectivity bandwidth to accommodate all concurrent users. The one that do has (Location 3), can still benefit from using eCDN, but without having to deploy and maintain infrastructure locally.

This is how eCDN could be deployed and configured:

  • HQ: Install Local eCDN node which pulls from Internet
  • Location 1: Install Local eCDN node which pulls from Internet
  • Location 2: Install Local eCDN node which pulls from HQ
  • Location 3: No local eCDN node and pulls directly from HQ

By using eCDN, we were to tackle the bandwidth bottlenecks in both internal and external networks and provide a great user experience.

So, how should I think about eCDN?

Think about it as your bandwidth saver, your network stabilizer when it comes to delivering enterprise video. Reduced bandwidth will avoid extra network infrastructure and expenditure, and will allow room for your audience to grow maintaining the best user experience.

Want to know more? Watch the webinar “Key Tips for a Successful Video Delivery.

 

Let’s Get Going