m

 


m


m 






INTRODUCTION

Web applications' traffic demand fluctuates

widely and unpredictably.

By leveraging an infrastructure cloud's on-

demand, pay-per-use capabilities, we finally can
match the capacity with the demand in real time.

We propose a client-side load balancing

architecture, which can scale and handle failure
on a millisecond time scale.


!

One existing approach, the earlier version of

Netscape, requires modification to the browser.

Smart Client, developed as part of the WebOS

project requires Java Applets to perform load
balancing at the client.

Java Applets require the Java Virtual Machine,

which is not available by default on most
browsers.

If the user accidentally agrees, a Java Applet

could have full access to the client machine.

Smart Client still relies on a central server to
download the Java Applet and the server list.

DNS server caches the IP address information. Thus,

all browsers contacting the same DNS server would
get the same IP address.
  !

Propose client-side load balancing architecture.

We use JavaScript technology to handle all load-

balancing details.

Our evaluation shows that our proposed

architecture can indeed scale linearly as demand
increases.
! m"
m
MODULES

#
$%&
The load balancer assumes the IP address of
the web application, so all communication with
the web application hits the load balancer first.

The load balancer is connected to one or

more identical web servers in the back-end.

The hardware-based load balancer is

designed to handle high- level of load, so it can
easily scale.

 #
$%'(&
Another well established technique is DNS aliasing.

When a user browses to a domain (e.g.,

www.website.com), the browser first asks its local DNS
server for the IP address (e.g., 209.8.231.11), then, the
browser contacts the IP address.

)*''+'#&
One way, referred to as direct web server return.

Another variation, TCP handoff,A browser first

establishes a TCP connection with a front-end dispatcher.

Before any data transfer occurs, the dispatcher

transfers the TCP state to one of the back- end servers,
which takes over the communication with the client.
SYSTEM CONFIGURATION

H/W System Configuration:

Processor - Pentium ²III

Hard Disk - 20 GB

RAM - 256 MB
S/W System Configuration:

Operating System : Windows95/98/2000/XP

Application Server : Tomcat5.0 and Tomcat Cluster
Server
Front End : HTML, Java, JSP
Scripts : JavaScript.
Server side Script : Java Server Pages.
Database : Ms Access
Database Connectivity : JDBC.