Varnish Dynamic Page Caching & Cache Purging vs Nginx+Redis

[Tom Anheyer | BerlinOnline]

Hi,

in our case (berlin.de) we use mosltly the standard ttl of 2mins. So we have no need for a persistent cache storage.
There a configuration tricks to combine two or more varnishd instances to act as a cluster with a "shared" cache.
Maybe this helps: https://info.varnish-software.com/blog/creating-self-routing-varnish-cluster

tom

Am Mittwoch, den 28.07.2021, 16:15 +0400 schrieb s s:
Hi Tom,
   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:

1) A single shared cache storage backend that can be used by multiple Nginx/etc. servers in a cluster.
2) Scalability (of storage capacity and of write+read throughput) and high availability via clustering with auto sharding & replication.
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.

Does Varnish provide the above capabilities (either on its own or in combination with other tools)?  If not, is it on the roadmap?

Thanks again for your help,
Sal

28.07.2021, 13:49, "Tom Anheyer | BerlinOnline" <tom.anheyer at berlinonline.de>:
Hello,

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.

tom

Am Dienstag, den 27.07.2021, 14:16 +0400 schrieb s s:
Hello all,
   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.

Thanks and Best Regards,
Sal

_______________________________________________

varnish-misc mailing list

<mailto:varnish-misc at varnish-cache.org>

varnish-misc at varnish-cache.org



<https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc>

https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc






,

_______________________________________________
varnish-misc mailing list
varnish-misc at varnish-cache.org<mailto:varnish-misc at varnish-cache.org>
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

--

Tom Anheyer
Senior Developer

BerlinOnline Stadtportal GmbH & Co. KG
Alte Jakobstraße 105
10969 Berlin
Germany

Tel.: +49 30 2327-5210
Fax: +49 30 2327-5596
E-Mail: tom.anheyer at berlinonline.de<mailto:tom.anheyer at berlinonline.de>

berlin.de | berlinonline.net

Amtsgericht Berlin-Charlottenburg, HRA 31951
Sitz der Gesellschaft: Berlin, Deutschland
USt-IdNr.: DE219483549

Persönlich haftender Gesellschafter:
BerlinOnline Stadtportalbeteiligungsgesellschaft mbH
Amtsgericht Berlin-Charlottenburg, HRB 79077
Sitz der Gesellschaft: Berlin, Deutschland

Geschäftsführung: Olf Dziadek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20210728/ec929e40/attachment.html>