If you’re familiar at all with Varnish, you know it improves content delivery performance by storing a copy of your content in cache, and every request thereafter is fulfilled by the cached content.
In the final installment of this series on managing dynamic CDN content, I will illustrate how Varnish Cache puts together the ideas of direct cache invalidation and TTL management to manage dynamic content. (Check out parts one and two of the series to get the whole story.)
In the first part of this series on managing dynamic CDN content, I explained how to use direct cache invalidation for caching dynamic content. In this second part, I’ll address TTL management as a method for meeting the particular challenges presented by dynamic content and CDNs.