![]() Thus the HA mode is achieved with duplicated origins: Once deployed, a successful installation window appears with the CDN URL which actually refers to the same endpoint the existing environment does. Find the Premium CDN add-on for the second environment and initiate installation.Ĭhoose Link to an existing environment option and pick the environment with previously installed CDN add-on and click on Install button.Ģ. Follow the steps below to make the required settings:ġ. In other words, CDN will be caching the static assets from several origins which are fully synced. It is implemented as a possibility to link several environments to the same CDN endpoint. So if you have the application which consists of two environments are fully synchronized, you can ensure its extra high availability with respect to the static assets cached at PoPs. Link Multiple Environments For Extra High-Availabilityįor multi environment solutions such as geo-distributed applications, the high availability is quite important for dynamic content as well as for static. The cache renewal process is much faster compared to the first static assets propagation after Add-On installation. Meanwhile, Purge All deletes all static assets at the PoPs, just asking the user to confirm cache clearance. Purge deletes specific assets within the specified path. Once the assets are deleted, the CDN begins downloading their fresh copies from an origin server. Purge, Purge All and Uninstallįor cache cleaning of the static assets at PoPs, we can use Purge or Purge All actions. It eliminates the necessity to perform any manual actions during scaling events. Primary Failover (PF) - all requests are sent to the first node, if it becomes unavailable the requests are redirected to the next and so on.ĭuring horizontal scaling of the nodes in the application server layer, the platform automatically updates the records of available nodes inside CDN service.Round Robin (RR) - even distribution of requests among available nodes.Within the above-mentioned add-on settings, you can also choose an appropriate method to ensure high-availability mode. Once you’ve applied this, the static website content will be available via your custom domain. Then follow the instructions on how to bind custom domain via CNAME record. You can specify multiple domains separating them by space or semicolon ( ). Press the Add-Ons button of the application server instance.ģ. When the installation is finished, you will get a success popup window with the CDN URL in the following format: Note : Pricing may vary depending on country and chosen service providers.ģ. In the opened window, choose the environment (Magento, in our case) where CDN should be enabled, the preferred nodes layer and press Install. Log in to Jelastic dashboard, open Marketplace, find the HTTP/3 Premium CDN Add-On and click Install. The demo instruction is based on Magento Hosting package where this e-сommerce platform can be automatically installed in one click and hosted within Jelastic PaaS. In this tutorial, you’ll see how to do that with Premium CDN service to ensure extremely fast content distribution among your clients worldwide. ![]() Jelastic customers get premium traffic for the same price across all continents and countries with no surprising bills based on geographic locations.Īttaching CDN network to a website is a simple process while using Jelastic PaaS. ![]() This CDN network spans the globe with 130+ Super PoPs (points of presence) located on 6 continents. ![]() Jelastic HTTP/3 Premium CDN (content delivery network) add-on leverages a highly interconnected global network, featuring massive bandwidth capacity, advanced caching and acceleration strategies, fast-routing IP Anycast technology for powerful and lightning-fast performance over the globe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |