Scalable architecture

Scalable Architectures

The scalable and flexible design of VideoExchange allows you to custom design and scale your CDN. With VideoExchange you can design streaming farms, on-net CDNs and overlay CDNs that fit your network and volume requirements.

 

Cloud of delivery servers

VideoExchange turns regular servers into a cloud of core, fallback, overflow and edge delivery servers. Core servers are used to store all content and are the default servers for regular traffic. Fallback servers are identical servers in another datacenter, for maximum redundancy. OverFlow servers are used to burst hot assets and live streams. Edge servers are used for geographical bursting.

 

Cluster servers

Cluster servers per type into logical clusters, for instance per PoP. There is no need for specific storage devices or load balancers: VideoExchange manages asset distribution and load balancing. 

You can restore and migrate servers on the fly. Data loss? VideoExchange restores a server with a single click. Server old or full? Setup a new server and let VideoExchange migrate the accounts and content for you.


Network independent

Deploy a CDN in multiple network segments to geo optimize your network. Setup PoPs in multiple ISP networks for deeper network penetration. Add servers to core, fallback, overflow and edge PoP clusters to size the PoP capacity. Add PoPs to size the entire CDN and optimize regional capacity and QoS. A VideoExchange powered CDN has zero impact on the underlying networks: there is no need to replace hardware. There is no need to deploy unknown devices into your network.


Size your CDN

VideoExchange lets you start with a minimum investment. Start small and grow along with your customers. With just a few strategically placed servers you can offer a competitive, easy to use, professional and feature rich delivery service. When demand grows, add servers and PoPs. Add management servers. Size as you grow.

Scale VideoExchange

The VideoExchange software suite itself can be run parallelized on a single Linux server. 2 Servers is a bare minimum for redundancy. When the CDN grows, you can split database, management, reporting and redirection services over multiple servers. For larger size CDNs you can size by using database and server clusters.


Architecture design support

Our CDN architects are available to help your network engineers design an optimal CDN architecture. We will discuss your current network setup, the capacity, the bottlenecks. We will discuss your capacity requirements. Together we will design a CDN architecture that fits in your infrastructure and budget.