Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy. It typically speeds up delivery with a factor of 300 - 1000x, depending on your architecture and software. |
Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy. It is installed in front of any server that serves HTTP(S) and is configured to cache static and dynamic contents, like HTML, CSS or JS served by the web server. Varnish Cache typically speeds up delivery with a factor of 300 - 1000x, depending on your architecture and software. A high level overview of what Varnish does can be seen in this video https://www.youtube.com/watch?v=fGD14ChpcL4.
Single: simple, inexpensive and scalable solution especially for standard applications (e.g. Shopware)
Redundant: fail-safe, redundant and scalable solution for mission critical standard applications (e.g. Shopware)
Auto Scaling: automatically scales new Varnish Cache instances in case of increased requests for custom applications
A varnish cache is typically used by standard applications like Shopware, Magento, WooCommerce or TYPO3 to speed up page loading times. Often it is even part of the setup recommended by the manufacturer. Basically it can be said that current applications support the control of a varnish cache, so that an integration is possible without great effort.
Technically the Varnish Cache is placed before the respective web application and acts as a caching reverse proxy. All incoming requests are forwarded to the varnish. The Varnish Cache checks whether it already has the requested page in its cache. If the page is already in the cache, the Varnish Cache delivers it directly without forwarding the request to the application server. If the Varnish Cache does not already have the page in its cache, it forwards the request to the App-Server and caches the response. The Varnish Cache checks which resources are still needed to display the page and loads them automatically from the App-Server and cache them, too. The Varnish Cache supports Edge Side Includes (ESI), which make it possible to assign different cache behaviors to individual parts of a page.
In order to facilitate integration, root360 has preconfigured templates ready for use before Magento, Shopware or TYPO3, taking into account the specific requirements of each application. The developer documentation for Shopware, Magento and TYPO3 explains how to configure a Varnish Cache in each application. However, root360 supports you at every step.
Use Case | Description | Variant | Setup |
---|---|---|---|
installations of Shopware, Magento, WooCommerce, TYPO3 or similar |
| Single | 1 x EC2 |
mission critical installations of Shopware, Magento, WooCommerce, TYPO3 or similar |
| Redundant | 2 x EC2 |
Any application which supports the detection of IP-addresses of Varnish Cache instances. |
| Auto Scaling | Auto Scaling EC2 |
Version | known issues |
---|---|
5.x | |
6.x |
As we have a lot of experience with Varnish-Cache in high-performance and high-load scenarios, we can provide initial configurations as well as optimizing configurations specifically for your application.
If you want to request a Varnish Cache (root360), you can do so by sending an E-Mail to service@root360.de or creating a ticket in the ticket system.
Required Information | Explanation | Options |
---|---|---|
Which variant of Varnish Cache do you want? | We offer 3 different variants for different use cases. You can get advice from our team, which solution is the right one for you | Single, Redundant or Auto Scaling |
In front of which application should the Varnish Cache be placed? | We offer pre-configured templates for standard applications. For custom applications we offer individual configurations. | Magento, Shopware, TYPO3 or Custom |
For root360 Managed Services pricing please contact our Service Team.
INTERMEDIATE