When using a traditional CDN or caching system, creating user-centric security and access policies can be a complex and performance challenging undertaking. Not only do you have to pull user data from a backend, but you then have to apply the security policies from that data onto the request. VCL is an excellent candidate for the latter problem of applying security policies to requests. This leaves the problem of how you get user data (JSON) into VCL? How do you do that on a user-by-user basis? And how do you do that in a way where you keep backend communication to an absolute minimum, or put another way, serve as much data from cache as possible?
In the five or so months since we released the Varnish Plus Cloud product, currently available on Amazon Web Services (AWS) and Microsoft Azure - and coming soon on the Google Cloud Platform - we have had a number of inquiries from customers all over the world asking: What’s the difference between Varnish Plus and Varnish Plus Cloud? Moreover, why should customers choose Varnish Plus Cloud - what benefits does it offer? What makes up a Varnish Plus Cloud subscription, and what does Varnish Software provide as a part of the Cloud instance?