A Content Delivery Network (CDN) represents a popular and useful solution to effectively support emerging Web applications by adopting a distributed overlay of servers. A CDN consists of an original server (called back-end server) containing new data to be diffused, together with one or more distribution servers, called surrogate servers. Periodically, the surrogate servers are actively updated by the back-end server. Surrogate servers are typically used to store static data, while dynamic information. The decision process about these two aspects could be in contraposition. The latter technique instead exploits the redirection mechanism of the HTTP protocol to appropriately balance the load on several nodes. A new mechanism for redirecting incoming client requests to the most appropriate server, balancing the overall system requests load. Our mechanism leverages local balancing in order to achieve global balancing. A “better response time” server is usually chosen based on geographical distance from the client, network proximity; on the other hand, the overall system throughput is typically optimized through load balancing across a set of servers. A critical component of a CDN architecture is the request routing mechanism. DNS request routing, transport-layer request routing, and application-layer request routing. With application-layer request routing, the task of selecting the surrogate server is typically carried out by a layer-7 application, or by the contacted Web server itself. The actual implementation of our solution in a real system, so to arrive at a first prototype of a load-balanced, cooperative CDN network.
You are here: Home / bulk ieee projects 2013 / A Dynamic Load balancing distributed algorithm for a strategy in a real CDN Environment