loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
2009 33rd Annual IEEE International Computer Software and Applications Conference
Clustering Versus Shared Nothing: A Case Study
Seattle, Washington, USA
July 20-July 24
ISBN: 978-0-7695-3726-9
The massive growth of the Internet paired with the rise in dynamic website content has increased the need for scalable network architectures. While these various network architectures should be transparent to the client, the speed, reliability, and maintainability of the system depends on the particular architecture that is implemented. This paper will discuss the findings from a case study that tests the speed of two software architectures that are often implemented to build scalable web application systems. The first architecture is server clustering with shared resources. Server clustering can be defined as a group of servers that directly share resources and actively partitions work based on work loads. Thus client traffic to the cluster can be distributed across several physical machines each running an instance of the application server. The other architecture is a shared nothing design, where application servers do not share resources, except for a dispatcher (load balancer). This paper addresses the question, what is the performance overhead of adding application servers into a tiered system.
Index Terms:
shared nothing, clustering, load balance
Citation:
Jonathan Lifflancer, Adam McDonald, Orest Pilskalns, "Clustering Versus Shared Nothing: A Case Study," compsac, vol. 2, pp.116-121, 2009 33rd Annual IEEE International Computer Software and Applications Conference, 2009
Usage of this product signifies your acceptance of the Terms of Use.