Welcome to chapter 4, in which we’ll discuss the Varnish Configuration Language, or VCL as we’ll refer to it.
In chapter 1, we explained what Varnish is. In chapter 2, we went into detail about what’s new in Varnish 6. In chapter 3, we showed you how to control Varnish’s behavior using HTTP’s built-in caching mechanisms.
HTTP has solid caching features, as you’re aware after having read chapter 3. But in real-world scenarios you’ll often fall short, and you need some sort of configuration mechanism that allows you to customize the system beyond what’s possible in standard HTTP.
Varnish can do even better: instead of a configuration file, you get a programming language. If your question is: “Does this make Varnish edge computing technology?”, the answer is definitely “yes”.