This page explains the different types of caching, including when to use them.
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 EDJX CDN 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:
Multiple types of multimedia content, depending on the browser settings
Use longer (high number) TTLs for the following resource record types:
Records that point to your web server or CDN 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 expire time on the server.
When to purge the cache for a website:
You are running out of space on your local drive.
You know a website has been updated, but your local cache has not been refreshed with the new content.
You have thousands of daily visitors to your site, and you need to make an immediate change to a product launch.
You manage an e-commerce site, and you recently ran out of inventory for a hot item, which now needs to be removed from the site.
See Start Cache Purge for details.