Having your cake, and eating it too: Using Varnish to serve content from your new Drupal site...
For many website projects, the scariest thing is the 'big switch' - turning off the old platform and turning on the new one.
But what if there was another way?
One option is to keep both new and legacy systems running, but using a tool like Varnish to 'split' the traffic between the two systems, only going 'live' with sections as and when they are ready.
This is how we managed this exactly problem with www.ul.ie and in this presentation, I'll give a deep dive as to how we did it.
Topics to be covered include:
- Running your own Varnish instance vs using a 3rd Party provider such as Fastly.
- What is achievable 'out of the box' using Fastly
- Using VCL snippets to achieve more flexibility
- Going all the way with a custom VCL configuration - the risks and rewards
- Tricks to make sure Drupal works well in such a configuration
But what if there was another way?
One option is to keep both new and legacy systems running, but using a tool like Varnish to 'split' the traffic between the two systems, only going 'live' with sections as and when they are ready.
This is how we managed this exactly problem with www.ul.ie and in this presentation, I'll give a deep dive as to how we did it.
Topics to be covered include:
- Running your own Varnish instance vs using a 3rd Party provider such as Fastly.
- What is achievable 'out of the box' using Fastly
- Using VCL snippets to achieve more flexibility
- Going all the way with a custom VCL configuration - the risks and rewards
- Tricks to make sure Drupal works well in such a configuration