DADO: enhancing middleware to support crosscutting features in distributed, heterogeneous systems

Wohlstadter, Eric; Jackson, Stoney; Dévanbu, Prémkumar

doi:10.1109/icse.2003.1201198

Cited by 38 publications

(36 citation statements)

References 34 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several authors have proposed extensions to AOP specifically for asynchronous distributed systems, including event-based aspect-oriented programming (EAOP) [11], aspects with explicit distribution (AWED) [34], and distributed aspects for distributed objects (DADO) [46]. These focus on advising one-to-one remote object invocations and thus on a different distributed programming abstraction than implicit invocations, which are specifically designed for multicast (one-to-many) interaction.…”

Section: Distributed Aspectsmentioning

confidence: 99%

Aggregation for implicit invocations

Frischbier

Margara²,

Freudenreich

et al. 2013

Proceedings of the 12th Annual International Conference on Aspect-Oriented Software Development

View full text Add to dashboard Cite

Implicit invocations are a popular mechanism for exchanging information between software components without binding these strongly. This decoupling is particularly important in distributed systems when interacting components are not known until runtime. In most realistic distributed systems though, components require some information about each other, be it only about their presence or their number. Runtime systems for implicit invocations-so-called publish/subscribe systems-are thus often combined with other systems providing such information.Given the variety of requirements for information about interacting components across applications, this paper proposes a generic augmentation of implicit invocations: rather than extending a given publish/subscribe API and system in order to convey a particular type of information across interacting components, we describe domain-specific joinpoints that can be used to advise application-level invocation routers-so-called brokers-used by publish/subscribe systems. This enables aggregation of application-specific information to and from components in a scalable manner.After presenting our domain-specific joinpoint model, we describe its implementation inside the REDS publish/subscribe middleware. The empirical evaluation of our approach shows that: (a) it outperforms external aggregation systems, by collecting and distributing information with a limited overhead; (b) the deployment of new functionalities has virtually no overhead, even if it occurs while the publish/subscribe system is running.

show abstract

Section: Distributed Aspectsmentioning

confidence: 99%

Aggregation for implicit invocations

Frischbier

Margara²,

Freudenreich

et al. 2013

Proceedings of the 12th Annual International Conference on Aspect-Oriented Software Development

View full text Add to dashboard Cite

show abstract

“…AO-middleware technologies such as JBoss, Spring, GlueQoS [44], CAM/-DAOP [38], DADO [43], FAC [36] and Prose [39] do not support the evaluation of distributed context properties. Supporting those platforms in the code generation thus needs a similar approach as presented in the generation to JBoss.…”

Section: Revisiting the Requirementsmentioning

confidence: 99%

Modularity and Variability of Distributed Software Architectures through Multi-view Refinement of AO-Connectors

beeck

Dooren

Lagaisse

et al. 2013

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. This paper presents MView, a technique that enables the separation of various architect views on an architectural connector in distributed software systems. A distributed system faces a lot of variability in the functions that it needs to support, and the deployment environments in which it needs to execute. Modularity of functionality and composition is essential in achieving this variability. While state-of-the-art AO-ADLs focus on describing compositions using aspect-based connectors, there is no support for describing a connector across multiple architecture views. This is, however, essential for distributed systems, where run-time and distribution characteristics are represented in multiple views. This results in connectors that suffer from monolithic descriptions, in which the views of different architects are tangled. MView untangles these architect views by defining them in separate modules and specifying refinement relations between these modules. We have integrated MView in an ADL, called MViewADL, which is supported by an Eclipse-plugin that performs code generation to the JBoss and Spring middleware platforms. We evaluate MView in a content distribution system for e-Media. First is an assessment of the architect effort required for creating variations of that system, followed by an evaluation of the extent to which changes ripple through the architecture.

show abstract

“…3. Higher-level abstractions and generative mechanisms -The DADO project [4], [5] has shown how AOP can be used in a software development process to bypass the rigid layered processing by extending the middleware platform with new aspect-oriented modeling syntax and code generation tools. The FOCUS project [13] relies on manual identification of the application invariants, the specialization context and the specialization points within the middleware source, and manual writing of scripts to feed into a transformation tool that specializes the middleware sources.…”

Section: Related Workmentioning

confidence: 99%

A Generative Middleware Specialization Process for Distributed Real-Time and Embedded Systems

Dabholkar

Gokhale

2011

2011 14th IEEE International Symposium on Object/Component/Service-Oriented Real-Time Distributed Computing

View full text Add to dashboard Cite

Abstract-General-purpose middleware must often be specialized for resource-constrained, real-time and embedded systems to improve their response-times, reliability, memory footprint, and even power consumption. Software engineering techniques, such as aspect-oriented programming (AOP), feature-oriented programming (FOP), and reflection make the specialization task simpler, albeit still requiring the system developer to manually identify the system invariants, and sources of performance and memory footprint bottlenecks that determine the required specializations. Specialization reuse is also hampered due to a lack of common taxonomy to document the recurring specializations. This paper presents the GeMS (Generative Middleware Specialization) framework to address these challenges. We present results of applying GeMS to a Distributed Real-time and Embedded (DRE) system case study that depict a 21-35% reduction in footprint, and a36% improvement in performance while simultaneously alleviating97% of the developer efforts in specializing middleware.

show abstract

DADO: enhancing middleware to support crosscutting features in distributed, heterogeneous systems

Abstract: Some "non-' or "extra-functional" features, such as reliability, security, and tracing, defy

Cited by 38 publications

References 34 publications

Aggregation for implicit invocations

Aggregation for implicit invocations

Modularity and Variability of Distributed Software Architectures through Multi-view Refinement of AO-Connectors

A Generative Middleware Specialization Process for Distributed Real-Time and Embedded Systems

Contact Info

Product

Resources

About