Presented by, R.Veera Narayana Reddy M.Naveen R.D.Satheesh G.Subrahmanyam

we finally can match the capacity with the demand in real time. We propose a client-side load balancing architecture.INTRODUCTION Web applications' traffic demand fluctuates widely and unpredictably. which can scale and handle failure on a millisecond time scale. . pay-per-use capabilities. By leveraging an infrastructure cloud's ondemand.

EXISTING SYSTEM One existing approach. the earlier version of Netscape. developed as part of the WebOS project requires Java Applets to perform load balancing at the client. which is not available by default on most browsers. If the user accidentally agrees. Java Applets require the Java Virtual Machine. . Smart Client. a Java Applet could have full access to the client machine. requires modification to the browser.

. Thus. all browsers contacting the same DNS server would get the same IP address. DNS server caches the IP address information. Smart Client still relies on a central server to download the Java Applet and the server list.

Our evaluation shows that our proposed architecture can indeed scale linearly as demand increases. We use JavaScript technology to handle all loadbalancing details. .PROPOSED SYSTEM Propose client-side load balancing architecture.


MODULES Load Balancer: The load balancer assumes the IP address of the web application.level of load. so it can easily scale. so all communication with the web application hits the load balancer first. The hardware-based load balancer is designed to handle high. . The load balancer is connected to one or more identical web servers in the back-end.

Before any data transfer occurs.A browser first establishes a TCP connection with a front-end dispatcher.g. 209.end servers. which takes over the communication with the client. Layer 2 Optimization: One way. When a user browses to a domain (e. DNS Load Balancing: Another well established technique is DNS aliasing. referred to as direct web server return. the browser contacts the IP address.8.231. Another variation. the browser first asks its local DNS server for the IP address (e. . then.11).. the dispatcher transfers the TCP state to one of the back.g. TCP handoff.

SYSTEM CONFIGURATION H/W System Configuration: Processor Hard Disk RAM Pentium ²III 20 GB 256 MB .

.S/W System Configuration: Operating System Application Server Front End Scripts Server side Script Database Database Connectivity : Windows95/98/2000/XP : Tomcat5.0 and Tomcat Cluster Server : HTML. : Java Server Pages. JSP : JavaScript. : Ms Access : JDBC. Java.

Sign up to vote on this title
UsefulNot useful