Edge Caching

An edge cache stores resources closer to the end user, using EDJX Nodes that reside at the edge of the network. Edge caching reduces stress on large networks and speeds up content delivery to the customer. When you set the edge cache, you tell the EdjCDN how long to cache a resource in the EDJX peer-to-peer (P2P) network.

A browser cache temporarily stores data in a user’s web browser and their local drive. Storing the files locally allows users to retrieve static resources faster. Most websites communicate with a browser to update the content stored in the cache when it becomes obsolete. The browser deletes the old content and saves the content as needed.

You need to set the browser time to live (TTL) if you want to control when content is updated for your visitors.

A browser cache temporarily saves the following content types:

Use longer (high number) TTLs for the following resource record types:

Records that point to your web server or EdjCDN should have a higher TTL value, since they are rarely changed.

When changing a resource record, use a low TTL because the changes will not occur until the TTL expires.

When modifying dynamic websites, use a low TTL because content updates are more frequent.

Purging your cache means that you control when the content is removed from the cache rather than wait for the preset cache to expire on the server.

When to purge the cache for a website:

Client-side

Server-side

See Start Cache Purge for details.

EdjCDN uses TTL to identify how long to store data on the node before refreshing the content stored. Once the TTL expires, the network refreshes the data and the expiration time restarts.