A Distributed Control Law for Load Balancing in

Content Delivery Networks
ABSTRACT
In this paper, we face the challenging issue of defining and implementing an effective law
for load balancing in Content Delivery Networks (CDNs). We base our proposal on a formal
study of a CDN system, carried out through the exploitation of a fluid flow model
characterization of the network of servers. Starting from such characterization, we derive and
prove a lemma about the network queues equilibrium. 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 is capable to partially solve congestion issues
due to high client request rates, thus reducing latency while at the same time increasing content
availability.
SYSTEM ANALYSIS
EXISTING SYSTEM
In existing system, Request routing in a CDN is usually concerned with the issue of
properly distributing client requests in order to achieve load balancing among the servers
involved in the distribution network. Several mechanisms have been existed in the literature.
They can usually be classified as either static or dynamic, depending on the policy adopted for
server selection. Static algorithms do not need any data retrieval mechanism in the system, which
means no communication overhead is introduced. Dynamic load-balancing strategies represent a
valid alternative to static algorithms.
DRAWBACK IN EXISTING SYSTEM
 Not maintained heavy load balancing.
 Not deliver static and dynamic information at a same time.
EXISTING ALGORITHMS



Random balancing mechanism (RAND).
Random robin Algorithm (RR).
Least-loaded algorithm (LL).
Two Random choices (2RC).

there is a server called redirector. ADVANTAGES IN PROPOSED SYSTEM  We can considerably reduce the amount of overhead traffic produced with respect to a solution requiring data exchanging across the whole network.law balancing (CLB). cooperative CDN network to be used both as a proof-of-concept implementation of the results obtained through simulations and . data that change in time) is just stored in a small number of back-end servers. Eclipse FUTURE ENHANCEMENT Our future work will be devoted to the actual implementation of our solution in a real system.6 GHz.. the surrogate servers are actively updated by the back-end server. so to arrive at a first prototype of a load-balanced. PROPOSED ALGORITHM  Control. Periodically. SYSTEM REQUIREMENTS HARDWARE PROCESSOR RAM MONITOR HARD DISK SOFTWARE : : : : PENTIUM IV 2. Surrogate servers are typically used to store static data. together with one or more distribution servers. the design of a proper network management law is carried out by assuming a continuous fluid flow model of the network. while dynamic information (i.  The advantages of using local information exchange with respect to providing all nodes with status information. In some typical scenarios.PROPOSED SYSTEM CDN consists of an original server (called back-end server) containing new data to be diffused. SERVLET) BACK END : MS SQL 2000/05 OPERATING SYSTEM : Windows XP/07 IDE : Net Beans. called surrogate servers. 512 MB DD RAM 15” COLOR 40 GB FRONT END : JAVA (JSP. Intel Core 2 Duo.e.

Modules: 1). Dynamic 3). Static 4). Create CDN 5).as a playground for further research in the more generic field of content-centric network management. User i/f 2). Implementation .