title: Best High-Availability-Setup for Varnish
body: <p>I am searching for the best Setup for a High-Avalability-Setup for Varnish.</p>
  
  <p>The Standard-Setup with more than one Varnish-Instance, every Instance has it's own Caching-Storage and so every Instance does it's own request on the backend.</p>
  
  <p>The Varnish-Cache is not shareable between several servers, even if the Filesystem-Option for Varnish_Storage is used.</p>
  
  <p>There seems to be a High-Avalability-Option in Varnish plus (the commercial Product) - is it worth the price? Any RL-Experiences out there? ;-)</p>
  
  <p>As something "in between" i found this (kind of) hacky Solution, that does not Replicate the data, but forwards every Request to the other Varnish-Instances: <a href="http://guytabrar.co.uk/index.php/2016/02/04/varnish-cache-replication-with-vcl/" rel="nofollow noreferrer">http://guytabrar.co.uk/index.php/2016/02/04/varnish-cache-replication-with-vcl/</a></p>
  
  <p>Anything i have missed? More ideas worth investigating?</p>
  
  <p>Thanks for your thoughts!
  Carsten</p>