Here's the thing - Varnish is cool. Well made, purpose built - a great tool.
But I can't help but think that in quite a few cases, people are jumping to it to compensate for a lack of proper engineering at the application level. Rails likes to add timestamps so things won't cache? WHY are you caching them then? Change the behaviour of rails for goodness sake.
This may be because Varnish gets deployed by a different person/team than those writing the apps - the web-turned-php developers can get sloppy and a decent frontend engineer can speed things up again by tossing varnish in front and fixing things up (which is a very common situation in my experience).
Certainly varnish can compensate for a wide variety of problems.. but it's also one more thing to go wrong.
4 comments
[ 2.8 ms ] story [ 23.2 ms ] threadSeriously, I'd love to hear how easy a varnish setup is to debug. Apache rewrite rules are imperative as well, just not obviously so.
But I can't help but think that in quite a few cases, people are jumping to it to compensate for a lack of proper engineering at the application level. Rails likes to add timestamps so things won't cache? WHY are you caching them then? Change the behaviour of rails for goodness sake.
This may be because Varnish gets deployed by a different person/team than those writing the apps - the web-turned-php developers can get sloppy and a decent frontend engineer can speed things up again by tossing varnish in front and fixing things up (which is a very common situation in my experience).
Certainly varnish can compensate for a wide variety of problems.. but it's also one more thing to go wrong.