<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="text-align:left; direction:ltr;">
<div>Hi,</div>
<div><br>
</div>
<div>in our case (berlin.de) we use mosltly the standard ttl of 2mins. So we have no need for a persistent cache storage. </div>
<div>There a configuration tricks to combine two or more varnishd instances to act as a cluster with a "shared" cache.</div>
<div>Maybe this helps: <a href="https://info.varnish-software.com/blog/creating-self-routing-varnish-cluster">https://info.varnish-software.com/blog/creating-self-routing-varnish-cluster</a></div>
<div><br>
</div>
<div>tom</div>
<div><br>
</div>
<div>Am Mittwoch, den 28.07.2021, 16:15 +0400 schrieb s s:</div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<div>Hi Tom,</div>
<div> Thanks for the tip on ESI. Indeed, Redis is more commonly used as an object cache. There are, however 3 features provided by Redis that I hope are available with Varnish, namely:</div>
<div> </div>
<div>1) A single shared cache storage backend that can be used by multiple Nginx/etc. servers in a cluster.</div>
<div>2) Scalability (of storage capacity and of write+read throughput) and high availability via clustering with auto sharding & replication.</div>
<div>3) Both in-memory and persistent on-disk storage. This is useful, for example, in the event of a failure, after which the data persisted on-disk can be used to restart.</div>
<div> </div>
<div>Does Varnish provide the above capabilities (either on its own or in combination with other tools)? If not, is it on the roadmap?</div>
<div> </div>
<div>Thanks again for your help,</div>
<div>Sal</div>
<div> </div>
<div>28.07.2021, 13:49, "Tom Anheyer | BerlinOnline" <tom.anheyer@berlinonline.de>:</div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<div style="text-align:left">
<div>Hello,</div>
<div> </div>
<div>Varnish provides ESI (Edge Side Includes). By using ESI you can split your pages in static parts (cachable) and dynamic parts (not cacheable). Each ESI can be cached with different rules. In my opinion, it makes no sense to use redis as an HTTP cache.
I see the task of redis mainly as an object cache in the backend.</div>
<div> </div>
<div>tom</div>
<div> </div>
<div>Am Dienstag, den 27.07.2021, 14:16 +0400 schrieb s s:</div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<div>Hello all,</div>
<div> I am quite new to Varnish. I have been reading about both Varnish and Nginx+Redis for page caching, and I am particularly interested in dynamic caching and cache purging. I have read in a number of posts that Varnish is "more flexible" in this regard,
but without many additional details on this. Can you please explain what features Varnish provides for dynamic page caching and cache purging, especially which are not available (or are more limited) in Nginx+Redis? Please forgive me if my question is very
basic/ignorant. As I said, I am new to Varnish.</div>
<div> </div>
<div>Thanks and Best Regards,</div>
<div>Sal</div>
<pre>_______________________________________________</pre>
<pre>varnish-misc mailing list</pre>
<a href="mailto:varnish-misc@varnish-cache.org" rel="noopener noreferrer">
<pre>varnish-misc@varnish-cache.org</pre>
</a>
<pre> </pre>
<a href="https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc" rel="noopener noreferrer">
<pre>https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc</pre>
</a>
<pre> </pre>
</blockquote>
<div>
<pre> </pre>
<div style="width:80ch"> </div>
</div>
</div>
,
<p>_______________________________________________<br>
varnish-misc mailing list<br>
<a href="mailto:varnish-misc@varnish-cache.org" rel="noopener noreferrer">varnish-misc@varnish-cache.org</a><br>
<a href="https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc" rel="noopener noreferrer">https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc</a></p>
</blockquote>
</blockquote>
<div><span>
<pre>-- <br></pre>
<div style="width: 80ch;">Tom Anheyer</div>
<div style="width: 80ch;">Senior Developer</div>
<div style="width: 80ch;"><br>
</div>
<div style="width: 80ch;">BerlinOnline Stadtportal GmbH & Co. KG</div>
<div style="width: 80ch;">Alte Jakobstraße 105 </div>
<div style="width: 80ch;">10969 Berlin</div>
<div style="width: 80ch;">Germany</div>
<div style="width: 80ch;"><br>
</div>
<div style="width: 80ch;">Tel.: +49 30 2327-5210</div>
<div style="width: 80ch;">Fax: +49 30 2327-5596 </div>
<div style="width: 80ch;">E-Mail: <a href="mailto:tom.anheyer@berlinonline.de">tom.anheyer@berlinonline.de</a></div>
<div style="width: 80ch;"><br>
</div>
<div style="width: 80ch;">berlin.de | berlinonline.net</div>
<div style="width: 80ch;"><br>
</div>
<div style="width: 80ch;">Amtsgericht Berlin-Charlottenburg, HRA 31951</div>
<div style="width: 80ch;">Sitz der Gesellschaft: Berlin, Deutschland</div>
<div style="width: 80ch;">USt-IdNr.: DE219483549</div>
<div style="width: 80ch;"><br>
</div>
<div style="width: 80ch;">Persönlich haftender Gesellschafter:</div>
<div style="width: 80ch;">BerlinOnline Stadtportalbeteiligungsgesellschaft mbH</div>
<div style="width: 80ch;">Amtsgericht Berlin-Charlottenburg, HRB 79077</div>
<div style="width: 80ch;">Sitz der Gesellschaft: Berlin, Deutschland</div>
<div style="width: 80ch;"><br>
</div>
<div style="width: 80ch;">Geschäftsführung: Olf Dziadek</div>
<div style="width: 80ch;"></div>
</span></div>
</body>
</html>