Before you can send out RFIs and RFPs to vendors, you need a clear technology strategy.
Typically, Vendors will offer a solution based on their proprietary, locked-in chain of Technologies. Global CDN Operators will try to make their best-effort CDN technologies fit into Telco environments.
Telco R&D departments will copy-paste technologies from best-effort Global CDNs.
Choosing and designing a CDN starts with the strategic, tactical and commercial goals. So how can you achieve these: do you have the right knowledge level? Do you have the staff to manage, market, sell and support a CDN?
The next step is to create a list of high level requirements. This will help you pre-select technologies and Vendors. What requirements do your internal Projects and Customers have regarding delivery Technologies, delivery Guarantees, delivery Capacity, delivery Quality of Service, Management, Transparency, Feedback, Reports, Analytics and Workflow automation? Are DNS and caching good enough or do your Customers demand more Premium Technologies?
The third step is to dive deeper into your specific Requirements regarding the CDN’s infrastructure: on-net, off-net, global? Hybrid?
What impact does this have on the Network, and which Components need to be upgraded or added? Is the CDN going to be used in Mobile Networks?
The fourth step is to look at the value chain: do you need to integrate the CDN with specific existing components or third party workflow environments?
The fifth step is to discuss your operational requirements: do you want to operate the CDN in-house or do you want to outsource? Do you need knowledge-transfer?
To not-so-few CTOs these and many other questions are new, but you see, this is our daily breakfast so we’re happy to help you through it together.
- Date: Apr 4, 2016