Tranquility: A Low Disruptive Alternative to Quiescence for Ensuring Safe Dynamic Updates

Vandewoude, Yves; Ebraert, Peter; Berbers, Yolande; D'Hondt, Theo

doi:10.1109/tse.2007.70733

Cited by 127 publications

(114 citation statements)

References 7 publications

Supporting

Mentioning

104

Contrasting

Unclassified

Order By: Relevance

“…As opposed to conventional software changes, which occur off-line and require re-deployment of the application, in this context we need dynamic reconfigurations where certain components are deployed and bound to the application as it is running. This requires revisiting and enhancing previous work on dynamic reconfiguration ( [45,63]). 5.…”

Section: Discussionmentioning

confidence: 99%

A formal approach to adaptive software: continuous assurance of non-functional requirements

2012

View full text Add to dashboard Cite

Abstract. Modern software systems are increasingly requested to be adaptive to changes in the environment in which they are embedded. Moreover, adaptation often needs to be performed automatically, through self-managed reactions enacted by the application at run time. Off-line, human-driven changes should be requested only if self-adaptation cannot be achieved successfully. To support this kind of autonomic behavior, software systems must be empowered by a rich run-time support that can monitor the relevant phenomena of the surrounding environment to detect changes, analyze the data collected to understand the possible consequences of changes, reason about the ability of the application to continue to provide the required service, and finally react if an adaptation is needed. This paper focuses on non-functional requirements, which constitute an essential component of the quality that modern software systems need to exhibit. Although the proposed approach is quite general, it is mainly exemplified in the paper in the context of service-oriented systems, where the quality of service (QoS) is regulated by contractual obligations between the application provider and its clients. We analyze the case where an application, exported as a service, is built as a composition of other services. Non-functional requirements-such as reliability and performance-heavily depend on the environment in which the application is embedded. Thus changes in the environment may ultimately adversely affect QoS satisfaction. We illustrate an approach and support tools that enable a holistic view of the design and run-time management of adaptive software systems. The approach is based on formal (probabilistic) models that are used at design time to reason about dependability of the application in quantitative terms. Models continue to exist at run time to enable continuous verification and detection of changes that require adaptation.

show abstract

Section: Discussionmentioning

confidence: 99%

A formal approach to adaptive software: continuous assurance of non-functional requirements

2012

View full text Add to dashboard Cite

show abstract

“…Of most relevant work in this area, quiescence [1] causes a high disruption to the running system that is not acceptable in many critical systems [7]. To address this issue, Vandewoude et al [8] proposed the concept of tranquility, as a low disruptive alternative to quiescence: Definition 1 (Tranquility). A component is tranquil if: (i) it is not currently engaged in a transaction that it initiated; (ii) it will not initiate new transactions; (iii) it is not actively processing a request; and (iv) none of its adjacent components are engaged in a transaction in which both of them have already participated and might still participate in the future.…”

Section: Problem Settingmentioning

confidence: 99%

A Safe Stopping Protocol to Enable Reliable Reconfiguration for Component-Based Distributed Systems

Ghafari

Heydarnoori

Haghighi

2015

Fundamentals of Software Engineering

View full text Add to dashboard Cite

Abstract. Despite the need for change, highly available software systems cannot be stopped to perform changes because disruption in their services may consequent irrecoverable losses. Current work on runtime evolution are either too disruptive, e.g., "blackouts" in unnecessary components in the quiescence criterion approach or presume restrictive assumptions such as the "black-box design" in the tranquility approach. In this paper, an architecture-based approach, called SAFER, is proposed which provides a better timeliness by relaxing any precondition required to start reconfiguration. We demonstrate the validity of the SAFER through model checking and a realization of the approach on a component model.

show abstract

“…Approaches like quiescence [13] can protect the system against inconsistencies, but the involved interruption of service is not acceptable by numerous systems. Approaches such as tranquility [14] tries to reduce the duration of the service disruption by identifying the updated parts of the system. However, such detection requires lots of data, not necessary available, about the system.…”

Section: From Componentizationmentioning

confidence: 99%

Describing Dynamism in Service Dependencies: Industrial Experience and Feedbacks

Escoffier

Bourret

Lalanda

2013

2013 IEEE International Conference on Services Computing

View full text Add to dashboard Cite

Abstract-The rise of dynamic applications is coming with new development challenges. Indeed, dynamism is a complex concern, difficult to perceive and manage by developers. In the context of a large industrial project dealing with fleet management, we had to deal with important environmental and evolutionary dynamism. To make it easier for the development team, we have used and extended the iPOJO service component model. This paper presents how the dynamism is described in component metadata and how it is managed at runtime. The extensions have been integrated into the Apache Felix iPOJO source code.

show abstract

Tranquility: A Low Disruptive Alternative to Quiescence for Ensuring Safe Dynamic Updates

Cited by 127 publications

References 7 publications

A formal approach to adaptive software: continuous assurance of non-functional requirements

A formal approach to adaptive software: continuous assurance of non-functional requirements

A Safe Stopping Protocol to Enable Reliable Reconfiguration for Component-Based Distributed Systems

Describing Dynamism in Service Dependencies: Industrial Experience and Feedbacks

Contact Info

Product

Resources

About