|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
INDEX TERMS
Primary Classification:
Keywords:
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...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||