Cache
Last updated
Last updated
The Edgeport platform offers caching on edge, a technique where a copy of your application content is stored in Points of Presence (PoPs) worldwide. This effectively reduces the load on your service's origin servers, leading to better application performance and enhanced request-handling capacity of your infrastructure. In addition, such an approach minimizes latency by shortening the distance between users and the websites they access, resulting in faster content delivery.
Moreover, we implement predefined edge caching rules based on the application type you’ve chosen when adding your service to the platform. For instance, default caching rules for WordPress enable the platform to bypass the specific dynamic requests directed to your origin and process them on edge if those are from logged users or concern eCommerce checkout experiences.
To manage your service's caching configuration, please refer to the Settings > Cache service menu section.
This screen includes two separate frames, allowing you to control the caching depending on the type of content requested - either Static or Dynamic cache.
After making any changes in this section, remember to click the Save button in the bottom right corner to apply them.
Please keep in mind that it may take up to 30 minutes for the new configurations to be fully distributed across all regions and PoPs.
The static cache encompasses a variety of assets vital for web content, including images, videos, CSS stylesheets, JavaScript files, and other essential web page elements. By caching these static resources, the page loading speed for data-intensive applications is significantly enhanced, resulting in quicker load times and an overall smoother user experience.
To enable or disable the static contents’ caching for your application, use the toggle within the same-named pane:
This option governs the caching of your service's static files exclusively for ADN platform(s), as CDN(s) already cache them by default.
Therefore, you may consider enabling it only in the case you’d like static content to be delivered through ADN rather than using CDN as configured initially.
Do not forget to click Save below.
Enabling this option initiates the caching of dynamic assets or blocks, which are distributed via your ADN platform(s), together with the static ones. Dynamic caching implies that frequently requested dynamic content, such as database-driven elements or real-time data, is temporarily stored on edge servers to improve response times and reduce the load on your origin servers.
To enable or disable the caching of dynamic assets for your application, click the toggle switch within the appropriate pane:
This controller manages the activation of both static and dynamic caching at once, so upon enabling it, the similar switch for the Static Cache in the pane above will be automatically turned off.
Do not forget to click Save below.
