Dynamic adaptation and deployment of distributed components in Hadas

Ben-Shaul, Israel; Holder, Ophir; Lavva, Boris

doi:10.1109/32.950315

Cited by 34 publications

(16 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…FRASCATI shares with component platforms, such as OPENCOM [17], HADAS [5], PRISM [38], LEGORB [35], K-COMPONENT [20], and the microkernel of JBOSS [24], several characteristics like introspection and reconfigurability. However, components with these models are finer-grained than SCA components with FRASCATI.…”

Section: Component Modelsmentioning

confidence: 99%

See 1 more Smart Citation

A component‐based middleware platform for reconfigurable service‐oriented architectures

et al. 2011

View full text Add to dashboard Cite

SUMMARY ThetextitService Component Architecture (SCA) is a technology‐independent standard for developing distributed Service‐oriented Architectures (SOA). The SCA standard promotes the use of components and architecture descriptors, and mostly covers the lifecycle steps of implementation and deployment. Unfortunately, SCA does not address the governance of SCA applications and provides no support for the maintenance of deployed components. This article covers this issue and introduces the FRASCATI platform, a run‐time support for SCA with dynamic reconfiguration capabilities and run‐time management features. This article presents the internal component‐based architecture of the FRASCATI platform, and highlights its key features. The component‐based design of the FRASCATI platform introduces many degrees of flexibility and configurability in the platform itself and it can host the SOA applications. This article reports on micro‐benchmarks highlighting that run‐time manageability in the FRASCATI platform does not decrease its performance when compared with the de facto reference SCA implementation: Apache TUSCANY. Finally, a smart home scenario illustrates the extension capabilities and the various reconfigurations of the FRASCATI platform. Copyright © 2011 John Wiley & Sons, Ltd.

show abstract

Section: Component Modelsmentioning

confidence: 99%

“…For example, Listing 1 depicts the descriptor corresponding to the assembly of Figure 1. The composite MyApp (lines 1-20) encloses two components: View (lines [3][4][5][6][7][8][9][10][11][12] and Model (lines [13][14][15][16][17][18]. In addition, MyApp exposes the service interface run (line 2), which is promoted from View.…”

Section: Introductionmentioning

confidence: 99%

A component‐based middleware platform for reconfigurable service‐oriented architectures

et al. 2011

View full text Add to dashboard Cite

show abstract

“…Compared to other approaches for adaptive distributed applications [2,6,7,1,10], our approach has certain advantages. First, because application variants are embedded in the adaptive application at design time and managed by coordinators, the application can perform and coordinate distributed adaptations at runtime without loss of data.…”

Section: Discussionmentioning

confidence: 99%

“…In the context of component-based adaptive distributed applications, some research [2,6,7] has proposed solutions for specifying the adaptation aspect of components, and/or providing mechanisms/frameworks for reconfiguring compositions of components. A few approaches have focused on adaptations of one distributed component that is deployed over many sites [1,6,10].…”

Section: Related Workmentioning

confidence: 99%

Model-driven development of component-based adaptive distributed applications

Phung-Khac

Beugnard

Gilliot

et al. 2008

Proceedings of the 2008 ACM Symposium on Applied Computing

View full text Add to dashboard Cite

This paper introduces an approach to develop componentbased adaptive distributed applications. Our approach separates the communication and the functional aspects of a distributed application and specifies the communication part as an abstract distributed component called the communication component. We then introduce a model-based process for automatically building many evolutionary variants of this component at deployment level, and integrating these variants into the target adaptive application that can dynamically select the running variant in order to adapt to the changing context. Thanks to an adaptation guide generated by the process, the adaptive application can coordinate distributed adaptations to (1) consistently transfer data of the replaced variant to the new one and (2) maintain the architectural coherence between distributed parts of the application. Hence, the target adaptive application can correctly adapt at runtime without loss of data. In this paper, we present the principle of our approach, illustrate it with an example, and show how we have automated the development process by model transformations.

show abstract

“…1 A computation unit performs only computation (by providing a set of methods) and does not invoke any computation outside itself. There are two kinds of connectors: (i) invocation connector, which is used to invoke a computation unit; and (ii) composition connector, which composes components.…”

Section: Towards Composition In Both Design and Deployment Phasesmentioning

confidence: 99%

Towards Composing Software Components in Both Design and Deployment Phases

Lau

Ling

Velasco-Elizondo

Component-Based Software Engineering

View full text Add to dashboard Cite

Abstract. In component-based software development, the design of components should be carried out separately from the deployment of components, in order to enable composition by independent third-parties. However, current component models are biased towards either the design phase or the deployment phase. In this paper, we argue that ideally component models should include both design and deployment phases, and it should be possible to compose components in both phases. We also demonstrate a preliminary implementation of composition in both phases in a component model we have defined.

show abstract

Dynamic adaptation and deployment of distributed components in Hadas

Cited by 34 publications

References 18 publications

A component‐based middleware platform for reconfigurable service‐oriented architectures

A component‐based middleware platform for reconfigurable service‐oriented architectures

Model-driven development of component-based adaptive distributed applications

Towards Composing Software Components in Both Design and Deployment Phases

Contact Info

Product

Resources

About