Content Caching is an application delivery performance enhancing feature that has traditionally only been found on dedicated devices or top end application delivery controllers.
The basic principle of a content cache is to store common responses to web requests such as images in an internal ‘cache’ and only send unique requests back to the web servers. This means that the content cache will respond to the end user on behalf of the web server. The benefit is that you will need less web servers because the load balancer cache is doing much of the work. In addition to this, the user will tend to get a better response time due to a reduction in back end traffic load and quicker transit times.
In this example, taken from an e-commerce customer's site, we can see that 81% of all the hits are actually being served from the jetNEXUS ALB-X cache. This could mean that you would need only 1 rather than 4 web servers to serve the same number of hits. Clearly this has significant cost savings in terms of web servers hardware, software licenses and maintenance.
Easy to Configure
The ALB X cache control GUI enables the intuitive configuration of complex reusable caching rules based on object type, name, directory, etc. This granular approach negates the need for complex configuration codes and time consuming operational maintenance, typical of other complex Content Caching appliances.
Define Content Expiry Time
For ecommerce users with a rapidly changing site, this feature of the jetNEXUS Content Cache allows rapid update of the cache.
Multiple Caching Profiles
Allows flexible configuration between separate sites.
Reduce Server Load:
The cache can significantly reduce load on back end servers which can dramatically improve page delivery times and therefore provide outstanding end user experience, especially during peak times. In fact one ecommerce user now reliably serves 94% of their content from the cache, significantly improving download times for their customers.
We'll send you a full report that is unique to your website, detailing exactly how much faster your site could be running with jetNEXUS and the type of bandwidth reductions you could experience.