Resources / guide / Article

One to Many

‍

‍

‍Explanation

A single application that requires more than one CDN configuration. This is usually due to elements within an application using different domains for different reasons.

‍

‍Best Practice

This is the ideal model for an application that uses static, dynamic and other content (streaming etc). Best practice would be to design the application with a different domain for each type of resource.

‍

‍Example

Application that has static, dynamic and streaming content:

  • Static.application.com
  • Dynamic.application.com
  • Streaming.application.com

This does not only split the CDN configuration making it easier to customise what is required from the CDN but also impacts cost (i.e. Static delivery is much cheaper than dynamic delivery).

‍

‍

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