Anevia to debut cloud-native CDN at IBC
At IBC 2019 in Amsterdam, Anevia will debut its NEA-CDN 5 cloud-native Content Delivery Network (CDN) solution in Europe. NEA-CDN is intended to let operators scale ...
At IBC 2019 in Amsterdam, Anevia will debut its NEA-CDN 5 cloud-native Content Delivery Network (CDN) solution in Europe.
NEA-CDN is intended to let operators scale their OTT services for peak viewing by adding their own CDN to their existing network infrastructure. Designed specifically for video streaming, it's intended to reduce network load by caching user requests and content to protect origin servers from multiple requests.
"Version 5 reduces or even eliminates the need for capacity planning," said Anevia NEA-CDN Product Manager David Tencer. "It is supplied as a container to be used with the Docker software platform. The container approach allows the service to be scaled for temporary or permanent requirements literally within minutes. This is also ideal for setting up a private cloud infrastructure to handle an OTT operator's mainstream traffic. Users can also add external cloud resources on the fly ahead of sports events that are likely to generate high viewing peaks."
"A second major benefit of using a container model is that processes are separated from the underlying hardware. In other words, it is no longer necessary to set up separate servers for the CDN and other processes. Operators can run their applications separately over the same private or public cloud infrastructure, within orchestrated containers. Combining a NEA-CDN with an Anevia origin server such as NEA-LIVE or NEA-DVR makes video delivery even more efficient, especially for live and near-live TV."
NEA-CDN 5 is orchestrated through the Kubernetes container management system. OTT operators can scale their service up and down by using virtual-machine hosts over an internal or external cloud infrastructure. An accessible Kubernetes cluster is required in addition to the NEA-CDN 5 configuration itself.
The NEA-CDN 5 is designed to be distributed geographically to cover multiple territories. It can be positioned close to end users at the edge of the CDN to optimize bandwidth requirements within the network. It can also be used with a NEA-CDN Balancer to handle large session amounts and maximize output traffic.