Knowledge Base

Search our articles or browse by category below

Get Started

Instructions for connecting the service and its initial configuration.

Billing & Payments

Overview of the features of billing and payment for the service.

Expert Support

Our team is happy to help you with all of your questions.

Anycast CDN

Overview of the aspects of working with Anycast CDN services.

Object Storage

Overview of the aspects of working with Object Storage services.

Profile settings

Overview of the aspects of working with Profile Settings.

Integration Guides

Overview of the aspects of integration with other services.

API token

Overview of the aspects of working with API integration.

Troubleshooting Guide

Overview of the aspects of CDN services troubleshooting.

Get Started

Powerful Global Network

Connecting everyone with fastest speed

5/5

General Questions

A CDN is a network of servers that distributes content from an “origin” server throughout the world by caching content close to where each end user is accessing the internet via a web-enabled device. The content they request is first stored on the origin server and is then replicated and stored elsewhere as needed.

Below are some of the advantages of using a CDN: Speed – A CDN helps improve the page load time of your site and makes it faster. Crash Resistance – Using a CDN allows you to distribute the load to multiple servers instead of having 100% traffic to our main server, thus making it less likely to crash.

Traditional web hosting relies on one server, while a CDN leverages a worldwide network of edge servers that disseminate content from a variety of interconnected hosts.

Cloud computing and CDNs are similar because they each serve content from geographically distributed servers. But this is where they vary: A CDN delivers content as quickly as possible, while cloud computing is based on flexibility, scalability and on-demand delivery of applications and data.

In a CDN, the edge servers are where the data is cached. CDN caching works roughly as per the following steps: An end user requests for static assets on your web page for the first time. The assets are retrieved from the origin server and once delivered are stored in the PoP edge caching server close to the end user.

As explained previously, in CDN, content is cached and stored on all the servers in a geographically distributed network. Now, when a user visits your website, the central server redirects his request to the server closer to his location and thus enhances your website’s performance by loading it faster.

The globally distributed nature of a CDN means reduce distance between users and website resources. Instead of having to connect to wherever a website’s origin server may live, a CDN lets users connect to a geographically closer data center. Less travel time means faster service.

CDNs serve up cached content so that the origin servers don’t have to deliver the same content over and over. Web hosting services charge for the data that is transferred to or from the origin server (this is often called “bandwidth”).

At the end of the day, CDNs and load balancers are fundamentally different types of tools. The main purpose of CDNs is to distribute content across a wide geographic area, whereas a load balancer distributes traffic across a network of servers that are usually in close geographic proximity to each other.