Resources / guide / Article

Many to One

‍

Explanation

More than one application can use the same CDN configuration. Many applications are designed on a template and differ only in content but not so much design. These applications can share the same CDN configuration.

‍

Explanation

It is most important to have specific requirements, checklists etc. of what qualifies the use of the same application. Making slight adjustments to the CDN configuration that is specific to each application can lead to other applications already using the that configuration to not work as expected. Applications based on the same template are perfect to be driven through a single CDN configuration.

‍

Explanation

A perfect example would be an application or website that only differed in content due to country or language.

All the domains above can share the same CDN configuration as long as the structure and the application builds are the same.

‍

‍

‍

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