Associate Director (Engineering & Innovation) at Husk Power Systems
Real User
Top 10
Jun 25, 2026
My main use case for Varnish Enterprise was to provide speed improvements for websites that we were creating for our clients through a SaaS service, which was a no-code website builder. We wanted to have Varnish Enterprise as a caching layer in between. This specific example was part of the website builder itself. When people created their own websites, they were hosted in our system and served through the Varnish Enterprise layer, functioning as a private CDN. We had servers closer to user locations from which we served these websites. Before and after implementation, there was a marked difference in the speed of the systems, and the users noticed it as well. There was significant improvement in the user experience.
Web Commerce Developer at a tech services company with 51-200 employees
Real User
Top 10
Apr 15, 2026
My main use case for Varnish Enterprise is mostly cache. When I say mostly cache, I mean we get directly into Varnish and we edit the rules with VCL files.
We implemented the solution for web caching in 2022. We auto-update the tool so that we don't face any security issues. We are a broadcasting company. We have many OTT clients that request a lot of images. We use a customized server that resizes images on the fly or transforms them in a different format. It’s a legacy product. It's no longer fully supported. We don't have much choice there, but getting any fixes is difficult. However, with our growth and volume over the years, these things just don't cope anymore. Ultimately, the traffic just kills the servers. So, we put Varnish in front of the cache and reduced the traffic to the service by about 98%. Instead of being bombarded with 40 million requests every day, it's now down to one million. We used more than 15 servers before. Now, with a bit of redundancy, we have reduced it to four. It is quite a lot. I haven't seen any issues on the server for one and a half years since we deployed Varnish, so it's pretty good.
Varnish Enterprise significantly boosts web performance through advanced caching, enhancing content delivery and handling high traffic volumes. The tool's customization with VCL and robust SSL/TLS support ensure adaptable, secure, and efficient operations across various industries, making it a critical solution for dynamic and high-demand websites.
My main use case for Varnish Enterprise was to provide speed improvements for websites that we were creating for our clients through a SaaS service, which was a no-code website builder. We wanted to have Varnish Enterprise as a caching layer in between. This specific example was part of the website builder itself. When people created their own websites, they were hosted in our system and served through the Varnish Enterprise layer, functioning as a private CDN. We had servers closer to user locations from which we served these websites. Before and after implementation, there was a marked difference in the speed of the systems, and the users noticed it as well. There was significant improvement in the user experience.
My main use case for Varnish Enterprise is mostly cache. When I say mostly cache, I mean we get directly into Varnish and we edit the rules with VCL files.
We implemented the solution for web caching in 2022. We auto-update the tool so that we don't face any security issues. We are a broadcasting company. We have many OTT clients that request a lot of images. We use a customized server that resizes images on the fly or transforms them in a different format. It’s a legacy product. It's no longer fully supported. We don't have much choice there, but getting any fixes is difficult. However, with our growth and volume over the years, these things just don't cope anymore. Ultimately, the traffic just kills the servers. So, we put Varnish in front of the cache and reduced the traffic to the service by about 98%. Instead of being bombarded with 40 million requests every day, it's now down to one million. We used more than 15 servers before. Now, with a bit of redundancy, we have reduced it to four. It is quite a lot. I haven't seen any issues on the server for one and a half years since we deployed Varnish, so it's pretty good.