WEB CACHE
BY
SUDHIR DAMA
08GE1A1251
WHY WEB CACHE?
Bandwidth Performance = Response Time Server Load
Failure Redundancy
WEB CACHING
1 HTTP request
2
1
Client1
HTTP response
2 1
Client2
2 1
2
Cache
Client3
Server
WHY CACHING IS IMPORTANT NOW
Web caching is a promising approach to the problem of rising Internet and Intranet traffic volume for three main reasons:
Quality of service Surge protection Overall traffic reduction
QUALITY OF SERVICE
Control speed of the path Reducing the potential for packet loss delays and speeding overall service Increases the transmission bandwidth to the browser for cached objects
Reducing long-distance transmission costs.
TRAFFIC SURGE PROTECTION
Help to reduce bandwidth demands during network traffic surges. Surges can swap any portion of a network, regardless of the network's bandwidth. Eliminates upstream traffic.
OVERALL TRAFFIC REDUCTION
Caches have a "hit" rate of 35%
Reduce upstream traffic on the network by that same percentage.
CACHING PRODUCTS LOOK LIKE
Web caching products come in two forms:
Appliances Software
CACHING APPLIANCES
Caching appliances from companies like NetApps and CacheFlow integrate caching software with a hardware platform and a proprietary operating system.
This appliances are flexible and platform independent
SOFTWARE
Caching software products run on standard operating system platforms such as UNIX and Windows NT. Caching software runs on the same operating system as other network management applications, the data generated by such a cache is easier to integrate with other network management functions.
ASSURING DATA FRESHNESS
A cache stores objects, and objects change over time. The cache must therefore determine the freshness of each object and replace outdated ones as they [Link] of freshness is: Get if modified Evaluate a stored object, and then retrieve a fresh copy Object was modified
HOW CACHES ARE CONFIGURED
A cache can be configured as a proxy for browser users, or it can be transparent to browser users Some additional engineering by the vendor, caches can also be configured as server accelerators, or "reverse proxy" caches
PROXY CACHES
A proxy cache operates by explicitly cooperating with the browser. The cache then either satisfies the request itself or passes on request to the server as a proxy for the browser. Proxy caches are particularly useful on enterprise Intranets
TRANSPARENT
CACHES
A transparent cache is so named because it works by intercepting the network traffic transparently to the browser. Transparent caches are especially useful to ISPs because they require no browser set-up modification Simplest way to use this cache internally on a network
SERVER ACCELERATORS OR REVERSE PROXY
A server accelerator is a proxy cache that stands in for one or more specific Web servers Server accelerator it reduces load on a particular server
CONCLUSION
I am in the opinion that it would be better if we can have a technology in such a way that a method should be originated to find exactly the web counts or "hits" of a particular web page/site, even though the clients access the cached servers.
THANK YOU