In our final blog in the series about differences between Varnish Enterprise and Varnish Cache, let’s highlight two major aspects of Varnish Enterprise that will be vital for many use cases. (For more, see Post 1: Project or Product and Post 2: Support Services)
In our second blog post in the series about differences between Varnish Enterprise and Varnish Cache (read part 1, Project or Product) , we’re going to focus on support and other professional services. Support encompasses all the guidance and help Varnish Software provides before, during and after Varnish is installed. It’s a crucial reason for Varnish Enterprise’s existence - many organizations require it.
This is the first in a short series of blog posts designed to help you understand the differences between Varnish Enterprise and Varnish Cache (check out post 2 on support services and post 3 on performance and security). It’s all about finding the right tool for the job; Varnish Enterprise and Varnish Cache are not in competition with each other. Whatever your content delivery goals, one of these Varnish solutions will be more suited to the task.
To begin, we’re talking about the differences between projects and products.
During the recent release of Varnish Enterprise 6.0.6, a significant amount of attention focused on in-process TLS.
But that’s not the only game-changing addition to the Varnish Enterprise technology stack. We now want to talk about Memory Governor, and what it means for everyone using Varnish Enterprise for streaming, web acceleration and content delivery.
Or, for those of the TL;DR persuasion: Memory Governor enables significant increases in memory availability and cache size.