Getting Started with a Content Delivery Network
By Mike Gioja, CIO SVP - IT Product Management, Development, Paychex
While the concept of a content delivery network (CDN) isn’t new, the use of these networks has evolved significantly since the 1990s when the World Wide Web exploded in popularity and search engine providers became mainstream users of CDN. Online news sites were the next adopters of the technology, followed by audio and video sites like YouTube, next was services like Dropbox and Microsoft OneDrive, and now, technology companies that offer software-as-a-service (SaaS) applications are turning to CDN to meet their needs and stay competitive when it comes to application performance, reliability, and cost savings, to name a few.
"Depending on your business, compliance concerns could be a major consideration"
A content delivery network is a system of distributed servers that deliver web pages and other web content to a user based on the geographic location of the user, the origin of the webpage, and a content delivery server. According to a report by MicroMarketMonitor, the North American content delivery network market is expected to grow from $1.95 billion in 2013 to $7.83 billion in 2019. This projected growth is largely due to how end users interact with online content, including the growth and popularity of things like streaming media, mobile devices, SaaS applications, and e-Commerce.
Content delivery networks offer a number of benefits to software-as-a-service technology companies, but before making the decision to jump in, it’s important to have an understanding of the benefits, what’s involved with using a CDN, and what to look for when evaluating providers.
Primary reasons why you should consider implementing a content delivery network:
• Performance. A CDN will improve the performance of your site or application by pushing static content out across the internet to datacenters in specified geographic locations. This improves the performance of your site by placing the data closer to the user, instead of grabbing it from a centralized datacenter.
• Reliability. With a CDN, you’re also protecting your users from feeling the impact of an outage if your data center goes down. In this instance, your data has already been copied onto your provider’s servers, allowing users to maintain access to your site and data, or depending on how you’re using a CDN, access and use of your application.
• IT Benefits and Cost Savings. A CDN will lower the network load of your own data center, resulting in higher performance, particularly during peak times due to higher numbers of visitors on a server consuming resources. Redirecting visitors to edge servers through CDN results in a more balanced network load. By creating this balance, you’re also cutting down on your content delivery costs.
Before moving to a CDN approach, consider the following:
• Understand Security. If you decide to use CDN and house your data on a network of servers, you need to do your research and make sure you understand compliance concerns. Depending on your business, compliance concerns could be a major consideration. Also keep in mind that you’re taking your users information that they trust you with and copying it to any number of different servers in your CDN, which opens it up to additional risk. Third-party providers offer varying levels of security features and options, but security threats still exist, and you become dependent on your provider’s ability to protect yours and your users’ data.
• Building you Knowledge and Skill Set. It’s important to understand that there will be a learning curve associated with implementing a CDN. Regardless of the provider you choose, they will do their part to help you with implementation and getting started, but there are additional factors to keep in mind. For instance, the use of a CDN will add additional levels of complexity to your development and deployment processes. Your IT team will need to research, and learn the different considerations and changes that will be necessary to make in the development process. Working with a vendor adds another level of complexity on its own. You need to take into consideration how their servers are configured, as well as understand their sensitivity to outages and how that will affect your customers. Being aware of and understanding these aspects will help you to limit exposure and negative impact.
• Use it because you Need it. While content delivery networks aren’t new, they’re use has evolved and steadily gained popularity with technology companies in the software-as-a-service space. However, CDN isn’t for everyone. It’s important for companies to make sure they have a true need for the benefits of CDN, and aren’t taking on additional complexities without needing or seeing the benefits.
If you’ve decided a content delivery network is right for your business, the next step is to evaluate vendors. Not all vendors are created equally, so here are just a few things to keep in mind when making your evaluations:
• Overlapping Footprints. Before selecting a CDN provider, make sure you understand where your content needs to be delivered. Are your users all U.S. based, or across the globe? Not all the vendors in the CDN space offer the same footprint, no make sure they have servers in all the areas your users are.
• Understanding your Use Case. Just as not all CDN providers have the same reach and footprint, they also have different areas of specialization, so it’s important to match your content type with the capabilities of a vendor. Some providers specialize in video and media, while others specialize in secure data and others yet in cloud storage, while some are more generalists. Because of this, it’s important to determine what’s most important to you and your business and find a provider best suited to meet your needs.
• Vendor Infrastructure. Talk to potential vendors about how they manage their infrastructure and determine if matches your business and what you need. By doing this, you’ll minimize some of the development and deployment complexities that come along with using a CDN.