Library Table of Contents Index Previous Next Comments

Reasons for pushing content to NetCache appliances

Centralized Internet data delivery is becoming less viable  Top

In the traditional model of content delivery with caching services, a user requests content, then the NetCache appliance obtains it from the origin server and delivers the content to the requesting users while caching it (if it is cacheable). The content is then available for the next client that requests it. The cache, therefore, is populated only as a result of user requests. This is the pull model of content delivery.

As the Internet is maturing, however, requirements by organizations that provide content to users are changing. Providers of content (for example, enterprises, content delivery networks (CDNs), service providers, and e-commerce vendors) want to be able to provide high-quality data reliably and quickly. With the growing use of multimedia and interactive content in particular, the centralized model of providing data from the center is no longer working well. The reason is that file sizes for multimedia are extremely large (unlike HTTP) and require large amounts of network bandwidth. Additionally, network congestion greatly affects the quality of the content that is delivered.

Providers of content are becoming increasingly interested in controlling content so that they can provide the best possible experience for their end users. They want to push content from the center of the network to remote offices, closer to end users, and they want to track the use of that content.

Benefits of pushing content close to users  Top

Some advantages of pushing content to NetCache appliances rather than relying on the traditional caching services model for populating a cache are as follows:

Library Table of Contents Index Previous Next Comments