Public instances and CDN caching

The cache on Magnolia public instances is separate from the cache on Content Delivery Networks (CDN) servers. In Magnolia, cache policies define whether the requested content is cached on Magnolia public instances. The decision to cache relies on voters.

It’s possible to have CDN servers that connect to Magnolia instances to get static resources, which are then stored on CDN servers for future requests. Typically, they are located closer to users, resulting in shorter round-trip latency. They can deliver content faster through network optimization instead of loading directly from Magnolia public instances. Furthermore, CDN caches eliminate the need for a request to travel to the public instances using different methods to populate the CDN cache.

DX Cloud is a digital Platform as a Service (PaaS) offering and includes an out-of-the-box content delivery network based on Fastly.
Feedback

DX Core

×

Location

This widget lets you know where you are on the docs site.

You are currently perusing through the Performance tuning guide docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules