CDN (Content Delivery Network) - CBA Glossary
📖 Glossary

CDN (Content Delivery Network)

A CDN distributes video streams across geographically distributed servers, ensuring viewers connect to nearby servers for faster delivery and lower latency. Without a CDN, all viewer traffic connects to a single origin server. With 100,000 concurrent viewers, that's impossible—one server can't handle the bandwidth. CDNs scale by distributing viewers across thousands of edge servers.

Technically, a CDN caches your video content on edge servers positioned in data centers worldwide. When a viewer in Abu Dhabi requests a stream, they connect to a CDN edge server in Abu Dhabi rather than traveling to your origin server (which might be in Europe or the US). Latency is lower, bandwidth from your origin is reduced, and viewer experience is better.

For Creative Broadcast Agency productions, CDN selection matters significantly. Events serving Middle East audiences benefit from CDNs with strong Middle East presence (Akamai, Cloudflare, or regional CDNs). Events with global audiences need truly global CDN coverage.

The economics: CDNs charge per gigabyte of delivered bandwidth or per concurrent viewer. A 1-hour broadcast to 10,000 concurrent viewers consuming 3 Mbps each uses roughly 1.35 terabytes of bandwidth (10,000 viewers × 3 Mbps × 3600 seconds ÷ 8 Mbps to TB/s). At typical CDN rates (AED 0.20–0.50 per GB), that's AED 270–675 for one hour. Cheaper than dedicated infrastructure for one event, expensive for daily streaming.

For large-scale events, we sometimes use multi-CDN strategies. Primary delivery uses your chosen CDN (good performance, reasonable cost). Secondary CDN provides redundancy—if primary CDN has issues, traffic failovers automatically. This costs more but ensures viewers never see outages.

CDNs also handle security. DDoS protection, geo-blocking (preventing viewers in certain regions from accessing), and token authentication (ensuring only authorized users can consume bandwidth) are standard CDN features. For premium events, we implement these controls.

FAQ
Do we need a CDN for corporate streaming to 500 employees?
+
Usually not. A single streaming server handles 500 concurrent viewers easily. CDNs become necessary when you exceed single-server capacity (typically 5,000+ concurrent viewers) or when geographic distribution matters (viewers globally need low latency).
Which CDN should we use?
+
Depends on audience geography and budget. Akamai is global and robust but expensive. Cloudflare is cheaper and decent for most uses. Regional CDNs (if available in your target regions) are sometimes better value. We evaluate audience geography and budget during planning.
Can we test CDN performance before the event?
+
Yes. Most CDNs allow test streams to your origin. We verify performance from different geographic locations and device types. If performance is unacceptable, we identify the issue (edge server latency, origin bandwidth bottleneck, network congestion) before the event.
What happens if the CDN fails during our broadcast?
+
Viewers experience interruption unless you have failover configured. With multi-CDN, traffic shifts to secondary CDN transparently. Without failover, viewers see buffering or connection errors. Failover infrastructure adds cost but is necessary for critical events.

Need help with cdn (content delivery network)?

Book a Discovery Call