Tranquility: A low disruptive alternative to quiescence for ensuring safe dynamic updates

  • Vandewoude Y
  • Ebraert P
  • Berbers Y
 et al. 
  • 57


    Mendeley users who have this article in their library.
  • 96


    Citations of this article.


This paper revisits a problem that was identified by Kramer and Magee: placing a system in a consistent state before and after runtime changes. We show that their notion of quiescence as a necessary and sufficient condition for safe runtime changes is too strict and results in a significant disruption in the application being updated. In this paper, we introduce a weaker condition: tranquillity. We show that tranquillity is easier to obtain and less disruptive for the running application but still a sufficient condition to ensure application consistency. We present an implementation of our approach on a component middleware platform and experimentally verify the validity and practical applicability of our approach using data retrieved from a case study.

Author-supplied keywords

  • Application-aware adaptation
  • Components
  • Componentware
  • Containers
  • Distributed objects
  • Middleware

Get free article suggestions today

Mendeley saves you time finding and organizing research

Sign up here
Already have an account ?Sign in

Find this document


  • Yves Vandewoude

  • Peter Ebraert

  • Yolande Berbers

  • Theo D'Hondt

Cite this document

Choose a citation style from the tabs below

Save time finding and organizing research with Mendeley

Sign up for free