For as long as I can remember, there has been this long standing debate inside the content delivery industry regarding which network architecture is better, one that is distributed or non-distributed. While many have opinions on the subject, to me, it's the content owner that decides which is best and not the vendor. Over the years I've spoken to hundreds of customers about the topic and frankly, I think it's time for the industry to redefine what it means to have a "distributed" network and the real metrics should be used when comparing one network to another.
Fifteen years after some of the first CDNs started delivering video, many of the CDNs still want to use their network architecture as a key selling point. While that's natural of any CDN to do, the problem is the way some go about doing it. Today, customers don't ask how many servers a content delivery network has and I can't remember the last time any content owner asked me how many servers any CDN has. While Akamai (AKAM) has spent the last ten years trying to convince everyone that a distributed network is the only way to properly deliver content, the market has shown us that there are now many different ways to deliver video with the a very good level of QoS.
In prior year's, Akamai's distributed network mantra was accurate. When CDNs first started to crop up in the market, they would start off with a few POPs and call themselves a CDN, even though they had very little coverage or capacity. But today, times have changed. The real questions customers ask are about capacity, coverage locations, quality of service and peering, not the number of servers. Those are the details content owners want to know and, as long as a CDN can deliver a good user experience, it doesn't matter to the customer if the network is distributed or non-distributed. How a CDN sets up their network is up to the CDN and most content owners don't care how they do it, only that the service they buy works with their expected level of quality.