Dealing with Personalized Content
SpiderCache's Unique Partial Page Caching Feature
Modern commercial web sites increasingly feature the individual personalization of pages for each user that accesses them.
This category of dynamic content – personalization – is an excellent example of data that does not play well with caching technology. It is highly volatile, low in statistical popularity, and has a user population of 1 -- not a great pedigree for caching eligibility. Yet, modern web sites increasingly feature some degree of personalization for most of their content, suggesting that these pages are off limits as viable candidates for caching. Warp’s answer to this challenge is at once simple and elegant – don’t cache the whole page. Cache only those impersonalized components of the page (dynamic or static) that warrant caching, and allow the remainder pass through to the web server.
SpiderCache’s Partial Page Caching feature provides the ability to select certain sections of the page to be cached, and others to remain “real-time” dynamic. This feature is enabled via HTML markup extensions, and ensures that content that needs to be delivered in real time can be, while the remainder of the page is cached.
For example, a web page may involve elements such as real-time stock quotes that change continuously, and weather updates that change perhaps twice a day. By allowing content to be cached on an as-needed basis, pages can reduce calls to the database and improve page responsiveness. Only minimal page markup is required to implement this solution. The SpiderCache solution also provides the means to pass values from an original non-cached execution of a dynamic page through to the cached instance. |
