Home > Research > Publications & Outputs > What is middleware made of?

Links

Text available via DOI:

View graph of relations

What is middleware made of?: exploring abstractions, concepts, and class names in modern middleware

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSNConference contribution/Paperpeer-review

Published
Publication date2012
Host publicationARM '12 Proceedings of the 11th International Workshop on Adaptive and Reflective Middleware
Place of PublicationNew York
PublisherACM
Number of pages6
ISBN (print)9781450316095
<mark>Original language</mark>English
Event11th International Workshop on Adaptive and Reflective Middleware, ARM 2012 - Co-located with ACM/IFIP/USENIX 13th International Middleware Conference - Montreal, QC, Canada
Duration: 3/12/20127/12/2012

Conference

Conference11th International Workshop on Adaptive and Reflective Middleware, ARM 2012 - Co-located with ACM/IFIP/USENIX 13th International Middleware Conference
Country/TerritoryCanada
CityMontreal, QC
Period3/12/127/12/12

Conference

Conference11th International Workshop on Adaptive and Reflective Middleware, ARM 2012 - Co-located with ACM/IFIP/USENIX 13th International Middleware Conference
Country/TerritoryCanada
CityMontreal, QC
Period3/12/127/12/12

Abstract

Developing appropriate abstractions for distributed programming is one of the core aims of middleware research. Yet, analysing the impact, diffusion, and success of these abstractions in concrete middleware code is difficult and time consuming. In this paper we propose to use the constituting words found in program identifiers to explore the concepts used in popular middleware platforms. We study and compare four industrial middleware products (JBoss, Hadoop, Axi2, and ActiveMQ), and show the existence of a substantial core of shared concepts that we think capture some of the key tenets of modern middleware engineering.