The Varnish Configuration Language (VCL), I'm sure you know already, is the source of Varnish versatility: by only enforcing the protocol flow and leaving the business logic to the user, Varnish can be easily configured to do things far beyond caching.

However, because the logic of websites is generally focused around hosts, and the VCL thinks in terms of processing steps, configuration may sometimes a bit odd, with the need to place safeguards around your code to ensure that logic for one host isn't applied to another one.

It works, but it can be tedious and unwieldy, so today we are going to have a look at how we can silo our VCL per website to achieve better maintainability.

The correlation between cloud/edge computing and security is growing stronger every day, and any caching/CDN solution loses value if it doesn’t deliver a set of features that can address this correlation by securing data and connections.

A couple of weeks back, we wrote about e-commerce on mobile, and how important device-specific performance has become in terms of securing your users’ experiences and ultimately conversions. While this is key to e-commerce, it’s also important for any company doing business online.

Blockchain fever has finally reached mainstream status with more than a thousand listed cryptocurrencies, and we feel that the world needs our contribution in this domain. This is why we are announcing the Varnish Cash solution.