ACM Home Page
Please provide us with feedback. Feedback
Optimizing layered middleware
Full text PdfPdf (210 KB)
Source Foundations of Software Engineering archive
Proceedings of the 5th international workshop on Software engineering and middleware table of contents
Lisbon, Portugal
SESSION: Optimization and evolution table of contents
Pages: 33 - 38  
Year of Publication: 2005
ISBN:1-59593-204-4
Authors
Ömer Erdem Demir  Kemper Hall, UC Davis Davis, California Republic
Premkumar Devanbu  Kemper Hall, UC Davis Davis, California Republic
Eric Wohlstadter  University of British Columbia, Vancouver, Canada
Stefan Tai  IBM Research, Hawthorne, New York
Sponsor
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 3,   Downloads (12 Months): 30,   Citation Count: 1
Additional Information:

abstract   references   cited by   collaborative colleagues  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1108473.1108481
What is a DOI?

ABSTRACT

Middleware is often built using a layered architectural style. Layered design provides good separation of the different concerns of middleware, such as communication, marshaling, request dispatching, thread management, etc. Layered architecture helps in the development and evolution of the middleware. It also provides tactical side-benefits: layers provide convenient protection boundaries for enforcing security policies. However, the benefits of this layered structure come at a cost. Layered designs can hinder performance-related optimizations, and actually make it more difficult to adapt systems to conveniently address late-bound requirements such as dependability, access control, virus protection, and so on. We present some examples of this issue, and outline a new approach, under investigation at UC Davis, which includes ideas in middleware, architectures, and programming models.


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
The Bandera Project web page. http://indus.projects.cis.ksu.edu.
 
2
The Indus static analyzer. http://indus.projects.cis.ksu.edu.
 
3
JacORB: Java implementation of the OMG Corba standard. http://www.jacorb.org.
 
4
Soot: a Java optimization framework. http://www.sable.mcgill.ca/soot/.
 
5
G. S. Blair, G. Coulson, A. Andersen, L. Blair, M. Clarke, F. Costa, H. Duran-Limon, T. Fitzpatrick, L. Johnston, R. Moreira, N. Parlavantzas, and K. Saikoski. The design and implementation of Open ORB 2. IEEE Distributed Systems Online, 2(6), 2001.
6
 
7
 
8
9
 
10
11
12
 
13
 
14
Object Management Group. The Common Object Request Broker Architecture. http://www.corba.org.
15
 
16
 
17
et al. Sarita Adve, Klara Nehrstadt. The GRACE project page. http://rsim.cs.uiuc.edu/grace/.
 
18
D. C. Schmidt and C. Cleeland. Applying patterns to develop extensible and maintainable ORB middleware. In IEEE Communications Magazine, volume 37, pages 54--63. IEEE CS Press, 1999.
 
19
K. Schwann. The DEOS project. http://www.cc.gatech.edu/systems/projects/DEOS/.
 
20
 
21
N. Wang, D. Schmidt, O. Othman, and K. Parameswaran. Evaluating meta-programming mechanisms for orb middleware. IEEE Communication Magazine, special issue on Evolving Communications Software: Techniques and Technologies, 2001.
 
22
 
23
24
 
25
D. Zook, S. S. Huang, and Y. Smaragdakis. Generating aspectj programs with meta-aspectj. In G. Karsai and E. Visser, editors, GPCE, volume 3286 of Lecture Notes in Computer Science, pages 1--18. Springer, 2004.

Collaborative Colleagues:
Ömer Erdem Demir: colleagues
Premkumar Devanbu: colleagues
Eric Wohlstadter: colleagues
Stefan Tai: colleagues