Drupal's Cache Metadata system paired with a Global CDN make a powerful combination. Drupal can inform the CDN which Drupal entities are within each page it serves. Then, when an entity is re-saved, the CDN clears from cache only the pages that contained that entity. Just turning on Pantheon Advanced Page Cache Module let's you take advantage of this power.
Sometimes you might want even more granular control of your caching behavior. That's when you need to write some code. Pantheon Agency & Community Engineer, Steve Persch and Capellic's Aaron Wolfe will go over how to customize caching behavior in Drupal 7 and 8.
Date: Thursday, February 15, 2018 at 11:00 am PST | 2:00 pm EST
Speakers: Steve Persch, Aaron Wolfe
Here’s what you’ll learn:
Basics of Full Page Caching
The majority of visitors to most Drupal sites are anonymous--they aren't signed in to the site. The site will load much faster when the HTML for one anonymous visitor can be cached and serve to the next visitor to the same page rather than having PHP generate the markup from scratch.
Drupal Cache Metadata and Pantheon's Global CDN
When your content is updated, only certain pages need to be cleared from the cache. Pantheon Advanced Page Cache module sends metadata from Drupal to our CDN so that the right pages are cleared and everything else stays cached.
Setting and Clearing Custom Cache Tags
One of the the most common places you may need to add your own custom tag is on a list of content. We will look at how to add such a tag with Views Custom Cache Tags and clear it with your own code in Drupal 8.
Using the Drupal 7 Backport
After being written for Drupal 7 the cache metadata system was backport to Drupal 7 to give you the same kinds of out of the box functionality. Customizing that functionality in Drupal 7 takes a little more work than it does in Drupal 8.