ACM Home Page
Please provide us with feedback. Feedback
Performance implications of design pattern usage in distributed applications: case studies in J2EE and .NET
Full text PdfPdf (847 KB)
Source International Symposium on Software Testing and Analysis archive
Proceedings of the ISSTA 2006 workshop on Role of software architecture for testing and analysis table of contents
Portland, Maine
Pages: 1 - 11  
Year of Publication: 2006
ISBN:1-59593-459-6
Authors
Jakub Rudzki  Solita Oy, Tampere, Finland
Tarja Systä  Tampere University of Technology, Tampere, Finland
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 10,   Downloads (12 Months): 129,   Citation Count: 0
Additional Information:

abstract   references   index terms   review   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1147249.1147250
What is a DOI?

ABSTRACT

In this paper, we investigate how design patterns used for designing remote interfaces influence the performance of distributed applications. The studied design patterns are considered 'good' designs. A choice between the designs can be made on the basis of their impact on overall application performance. The presented case study includes two functionally identical web applications: one implemented as a J2EE application and the other as a .NET application. The results obtained show that the choice of design pattern used for remote communication has an impact on the performance of the whole application. We evaluate which aspects of the design patterns and remote communication have a significant impact on performance. We also provide recommendations for the usage of the investigated design patterns: Façade, Command, and Combined Command. Finally, we provide some general guidelines that can help determine certain aspects of the design solutions that have an impact on performance in distributed systems.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
Apache. JMeter. http://jakarta.apache.org/jmeter, 2004.
4
5
6
 
7
W. Elbers, F. Koopmans, and K. Madlener. Java RMI and .NET remoting performance comparison. http://www.niii.ru.nl/marko/onderwijs/oss, December 2004. Radboud Universiteit Nijmegen.
 
8
 
9
10
 
11
JBoss EJB server. http://www.jboss.org, 2004.
 
12
JOnAS: Java Open Application Server. http://jonas.objectweb.org, 2004.
13
 
14
 
15
F. Marinescu. EJB Design Patterns. The MiddleWare Company, 2002.
 
16
J. Mattila. EJB Performance. Master's thesis, Tampere University of Technology, 2004.
 
17
Microsoft Corporation. .NET. http://msdn.microsoft.com/netframework, 2004.
18
 
19
MySQL. http://www.mysql.com, 2004.
 
20
P. Obermeyer and J. Hawkins. Microsoft .NET remoting: A technical overview. http://msdn.microsoft.com/library, July 2001. Microsoft Corporation.
 
21
 
22
J. Rudzki. How design patterns affect application performance - a case of a multi-tier J2EE application. In FIDJI, pages 12--23, 2004.
 
23
Sun Microsystems. Java 2 Enterprise Edition. http://java.sun.com/j2ee, 2004.
 
24
Sun Microsystems. Java Remote Method Invocation (Java RMI). http://java.sun.com/products/jdk/rmi, 2005.
 
25
The Middleware Company Case Study Team. J2EE and .NET (reloaded). yet another performance case study. http://www.gotdotnet.com/team/compare/Middleware30.pdf, June 2003.
 
26
D. Trowbridge, D. Mancini, D. Quick, G. Hohpe, J. Newkirk, and D. Lavigne. Enterprise Solution Patterns Using Microsoft .NET. Microsoft Corporation, 2003.
27


REVIEW

"Shantanu Bhattacharya : Reviewer"

Rudzki and Systä have done a good job of measuring the performance of various design patterns for a particular problem in the Java 2 Platform, Enterprise Edition (J2EE) and .NET. The conclusions drawn are also useful, but, like any other perf  more...

Collaborative Colleagues:
Jakub Rudzki: colleagues
Tarja Systä: colleagues