|
|
||
Overview > Eliminating Duplication > Ensuring Content Freshness > Partial Page Caching > Identifying Unique Content > Spidercache Advantages > SpiderCache Product Family |
||
|
||
The SpiderCache AdvantageSpiderCache is an all-software solution that has been designed from the ground up for rapid deployment and ease of use, as well as for more elaborate configurations that allow site administrators and developers to take full advantage of dynamic content caching. SpiderCache’s management tools demonstrate industry-leading ease of installation and configuration, allowing site administrators to begin caching their sites more rapidly than any other solution on the market. Cache Control FlexibilityUnlike other dynamic content caching solutions that rely solely on TTL (Time-to-Live) mechanisms, SpiderCache provides exceptional flexibility and control for website administrators with responsibility for the dynamic caching environment. SpiderCache’s unique Parameterized Caching allows page elements to be cached on a custom basis, according to one or more of the following criteria:
Parameterized Caching enables administrators to achieve highly granular caching levels that competitive solutions cannot begin to match. Page elements can be cached based on a query string alone, or for more advanced caching scenarios, http header and cookie information can set the criteria for caching. For example, dynamic files that respond in a particular manner according to a user’s browser type, such as Internet Explorer or Netscape, can be cached seperately. Content based on personalization can also be cached, such as user-specific language or location choices. SpiderCache goes well beyond other dynamic content caching solutions by introducing “only-if,” “only-if-not,” and “ignore” logical scenarios. These inclusive and exclusive parameter requirements are used to further refine caching criteria. For example, an administrator could cache all instances of a page, save one, or vice versa. Here’s a real-world scenario: all instances of a page except those whose users are from New York could be cached. Conversely, no instances of that page could be cached except for users from New York. This remarkable flexibility is achievable without source code changes to the page. Another example: sites with functionality based upon unique member IDs can use the “ignore” feature to cache every page instance, yet still track the patterns of individual users from page to page. This feature is key for eCommerce platforms that use unique member IDs, such as Microsoft Commerce Server. Caching EfficienciesWhen configuring SpiderCache for the optimum performance of a website, web administrators must determine which content is most suitable for dynamic content caching. Based on the general rule of 80/20—where 80% of requested dynamic content is identical and 20% is unique—the first step is to identify the content that receives the majority of site traffic. Once identified, analysis of the rate of change of the content will offer clues to the content’s caching appropriateness. Content that changes frequently, such as real-time stock quotes, can be refreshed and drawn from the cache, or left real-time with Partial Page Caching. Even if a particular content element changes every second, the page instance could be seen thousands of times before it is refreshed. SpiderCache gives administrators the flexibility to configure based on their unique needs. Preserving Log File IntegritySome caching solutions can change the way web usage is reported and logged, altering the integrity of log files. SpiderCache preserves log file integrity by logging the request, not the content that is served. SpiderCache also offers the option for administrators to log hits to the cache if desired. For example, if a page contains press release information, and receives 100 hits while cached, the log files would show a single request to the originating URL, and 99 to the cached file. A Catalyst for ChangeAs a performance tool, SpiderCache offers a number of benefits in addition to increased page speed and server overload protection. Site developers are finding that the ability to implement SpiderCache changes the way a site can be architected. Developers can now build site pages for maximum manageability, as calls to the database do not necessarily require significant overhead. SpiderCache empowers highly personalized sites that promise highly responsive dynamic content but that have never really delivered due to performance drawbacks. Leveraging the Benefits of Dynamic Content CachingSpiderCache has been carefully designed for rapid implementation, as well as for detailed caching configurations of dynamic content formats. By removing bottlenecks and freeing the server to concentrate on truly unique content, web developers can develop highly centralized and manageable sites that are exceptionally dynamic. SpiderCache can be very effectively implemented at the time of development. UsabilitySpiderCache’s Universal Plug and Play functionality allows administrators to realize performance gains the same day of installation, with no need to change site architecture. The SpiderCache solution has been designed for ease of management, and is simple to integrate into existing infrastructures. With SpiderCache’s GUI administration, users can finely tune their caching configurations on many levels, from Universal Plug and Play, to partial page caching and cookie-based caching. Users can also administer the cache through COM objects on Windows, or through a Perl programming interface on Linux. Features like a keyword manager and visual cache management allow an exceptional level of control and ease of use. ConclusionSpiderCache offers the means for businesses to provide exceptional service levels and enhanced scalability, creating more satisfied users and contributing directly to site revenues. SpiderCache is the most cost effective means to accelerate user experiences and provide an immediate return on investment, as well as helping to reduce IT costs for the enterprise. With SpiderCache, dynamic content can meet the needs of users by offering advanced site features, without placing an undue burden upon the server. By creating a cached instance of dynamic content, the server can treat a considerable portion of dynamic content as static, enabling pages to be delivered more than 35 times faster, with up to 5 times as many users served. |
||
