Reseñas de caché de barniz y detalles del producto
Varnish Cache es un acelerador HTTP de código abierto diseñado para sitios web dinámicos con mucho contenido, así como para API. Millones de sitios web lo utilizan para acelerar la entrega de contenido y reducir la carga del servidor. Varnish Cache es conocido por su flexibilidad y capacidad de configuración, lo que permite políticas de almacenamiento en caché personalizadas a través de su lenguaje de configuración Varnish (VCL). Admite almacenamiento en caché de alto rendimiento con requisitos mínimos de hardware, lo que lo convierte en una opción popular para empresas de todos los tamaños.
| Capacidades |
|
|---|---|
| Segmento |
|
| Despliegue | Nube/SaaS/basado en web, Linux de escritorio, Mac de escritorio, Windows de escritorio, Linux local, Windows local |
| Cursos | Documentación |
| Idiomas | Inglés |
Varnish is a highly effective caching technology that has assisted us in delivering fast web and streamlining experiences to vast audiences. It seamlessly handles work for content-heavy dynamic websites. From streamlining the handling of surges in demand to keeping expenses manageable the software integrates the adaptability of open-source technology to boost revenue and growth.
I've had a seamless experience while using Varnish Cache. However, have not faced any issues with its feature and consequently, there is nothing about this product that I don't like.
In our organisation, we use Varnish Cache as a performance acceleration tool to enhance the speed and reliability of our website.
It's supported natively by most of our hosting partners, easily integrated with our typical CMS (Drupal), and provides an immediate, impressive performance boost.
It can be difficult to configure at times, and is prone to being more persistent than expected.
Site performance, caching rendered pages in Drupal.
The amount of connections this will handle is massive. The configuration allows you to apply extremely granular control over when to use what backend, how long to cache something, and any number of routing considerations.
The configuration allows complete customization, with that it is also easy to shoot yourself in the foot. But running on Linux, most of us are accustomed to various foot-guns anyway, so I would say it's no different than anything else really.
Shields our backend servers from having to process PHP code constantly, becuase much of the content can be rendered once per day and served from cache. We also have "saint" configuration which will keep the site up even when the backend servers are non-responsive and as long as there is a cached version (even it it would have expired) will still serve content which adds to our uptime.