Varnish Cache relies on community input and needs and wants to hear from you. We invite you to participate in our brief user survey, which will take less than 2 minutes:
Varnish Cache is celebrating its 10th anniversary this year, and as a part of the festivities, we launched a competition to shine a spotlight on some of the superstar uses of Varnish Cache. There was some tough and creative competition, but we’ve identified our winners!
These lucky (or maybe it’s more talent than luck) winners will receive our branded Varnish Cache Swiss Army knife and, of course, our thanks and admiration for pushing Varnish Cache to new heights, lengths and into new territories.
We’re happy to announce that the winners are:
As we launch into the tenth-year anniversary festivities for Varnish Cache, we thought it would be a great time to dig into the history and take a look back at how your favorite web app accelerator started.
Quite a while back, I wrote the first part of this blog series about the challenges of cache invalidation with the dispatcher in Adobe Experience Manager 6.0 and Adobe CQ 5.x in any Linux platform (Adobe supports Red Hat running a Linux Kernel 2.6 and 3.x). So the context should be clear. But how do you actually go about replacing it?