One to Many

ExplanationA 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 PracticeThis 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).