-
-
Notifications
You must be signed in to change notification settings - Fork 139
Blob Cache
Patrick Bates edited this page May 5, 2024
·
1 revision
What began a few years ago as a wrapper around App Fabric Caching allowing for communication with PHP has matured into a robust full-page caching solution for WordPress and Project Nami installations running on Microsoft Azure.
A plugin for WordPress and Project Nami sites which writes page output to Blob Storage for later serving. Full headers are maintained in the cache, allowing transparent support for XML, JSON, etc. in addition to HTML. Posts are purged from the cache on save/update. Site admins may also purge individual pages via a button on the Admin Bar.View the source code on GitHub
Using the IIS Integrated Pipeline, this module intelligently examines requests to your web site for possible cache hits. (Logged in users automatically bypass the cache, along with other special cases.) When found, the page content is quickly retrieved from Blob Storage and served to the client, complete with reconstruction of the original response headers. PHP is never invoked for cache hits, greatly improving site performance and reliability.For further performance enhancement, MaxAge is set for short-term client caching. Support has also been added for returning 304 Not Modified to the browser if the copy in the server cache still matches the one in the client cache, reducing data transfer.
View the source code on GitHub
This WebJob scans your storage container for Blob Cache files and removes expired content on a schedule you set. Should be run at least daily to free up space and control costs, though we recommend hourly execution.View the source code on GitHub
Another WebJob, this one is essentially a spider which crawls your site and adds pages to cache in advance of browser requests. It is able to bypass the Blob Cache Module through the use of a pre-shared key which you define. You are able to control the pages the spider starts with, the depth at which it will crawl the site, and how often it runs to reload the cache. For best results, set the cache duration in the Blob Cache Plugin to slightly longer than the time between executions of this WebJob. Unlike other external caching solutions designed to be shared by a pool of web servers, the cost is quite minimal. Rather than paying for caching servers, you pay standard Blob Storage usage rates. Sites with several million page views per month will see charges well under US $5 per month, while smaller sites may pay less than US $1 per month. When properly configured with Blob Cache Loader, you can proactively put content into the cache and deliver an end-user experience better than most any other site based on WordPress. In addition to this site, here's some other examples so you can see for yourself...