Resources / guide / Article

CDN Models

Mapping website/application can be mapped to more than one CDN configuration or more than one application can be mapped to a single CDN configuration.

‍

The rules that should be followed to work out which CDN model to use as best practice are:

  • Does the website/application share the same Origin Server as another application?
  • Does the website/application share the same requirements (What type of CDN product is required)?
  • Does the CDN custom configuration match what is required for the new website/application?

Below are a set of diagrams (Diagram 4) that describes the relationship for each model.
Note: Understand that the models below are based on relationships between the End User (Application) and the Proxy Server (CDN). These models do not change if there are more than one Origin Server (hosting server) behind the CDN. If there is more than one Origin Server, the CDN can be configured to handle requests as required. There is no need to have more than one configuration if there is more than one Origin.
Diagram 4: All Relationship Models

‍

Are you ready to save money and outperform?

Related Articles

Guide
CDN World
Sep 19, 2023
TLS (SSL)
TLS ensures the privacy and data integrity between to communicating points across a network. Originally known as SSL, TLS is not only important when transferring sensitive data (such as personal or payment information) but also for websites/applications in general. Google have also announced that fully HTTPS websites/applications will have SEO priority.

Read more

Guide
CDN World
Sep 19, 2023
DNS: Domain Name System (Domain Name Server)
DNS is a vast protocol that is essentially its own subject entirely, however, within the scope of this document it is only important to understand the basics of DNS and how it is used when dealing with CDN vendors.

Read more

Guide
CDN World
Sep 19, 2023
Configuration
Referring back to Diagram 1, once requirements and add-ons have been decided, it is now time to look at customisation. Historically,

Read more

Guide
CDN World
Sep 19, 2023
Many to Many
Many applications that require many CDN configurations. These may or may not (but most likely do) reside across multiple origin servers. Most common in complex setups where a single application cannot serve the purpose of the whole website. As an example, this is commonly seen on trading or very large retail websites where each part of what may look like the same website/application are actually designed, implemented and managed by multiple teams across a business.

Read more

By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.
DenyAccept