Online application upgrade using edition-based redefinition

Choi, Alan

doi:10.1145/1656437.1656443

Cited by 7 publications

(10 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We do not rely on static typing but on dynamic scoping with first-class contexts, we address garbage collection, concurrency, and provide a working implementation. Oracle enables a table to have two versions that are kept consistent thanks to bidirectional "cross-edition triggers" [Cho09]. Schema evolution addresses the update of persistent object stores, which closely relates to dynamic updates.…”

Section: Development Effortmentioning

confidence: 99%

“…Bidirectional transformations were used in prior work [CYH + 11, Dug01, Cho09] to achieve dynamic updates, respectively for systems written in C [CYH + 11], from a type-theoretic point of view [Dug01], and for databases [Cho09]. However, neither of these approaches modeled context explicitly, nor did they tackle object-oriented systems, taking into consideration type safety, performance, concurrency and garbage collection all together.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Incremental Dynamic Updates with First-class Contexts.

Wernli¹,

Lungu²,

Nierstrasz³

2013

JOT

View full text Add to dashboard Cite

Highly available software systems occasionally need to be updated while avoiding downtime. Dynamic software updates reduce downtime, but still require the system to reach a quiescent state in which a global update can be performed. This can be difficult for multi-threaded systems. We present a novel approach to dynamic updates using first-class contexts, called Theseus. First-class contexts make global updates unnecessary: existing threads run to termination in an old context, while new threads start in a new, updated context; consistency between contexts is ensured with the help of bidirectional transformations. We show that for multi-threaded systems with coherent memory, first-class contexts offer a practical and flexible approach to dynamic updates, with acceptable overhead.

show abstract

Section: Development Effortmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Incremental Dynamic Updates with First-class Contexts.

Wernli¹,

Lungu²,

Nierstrasz³

2013

JOT

View full text Add to dashboard Cite

show abstract

“…Fixing bugs, adding new features, removing obsolete features, optimizing performance-all involve upgrading existing software systems. Moreover, current industry trends suggest that upgrade-related downtime is unacceptable for many large-scale distributed systems, such as electrical utilities, assembly-line manufacturing, customer support, e-commerce or online banking [6]. These systems must employ online-upgrade techniques.…”

Section: Introductionmentioning

confidence: 99%

“…However, industry trends suggest that online-upgrade techniques are currently needed in a wide range of distributed systems (e.g., electrical utilities, assembly-line manufacturing, customer support, ecommerce, online banking) [6]. The characteristics of distributed systems simplify some aspects of the upgrade problem, while complicating others.…”

Section: Introductionmentioning

confidence: 99%

“…System administrators sometimes favor the atomicity, by upgrading inter-dependent components together, during windows of planned downtime [9], or by placing the old version in a read-only mode during the upgrade. However, many enterprises can no longer afford the high cost of downtime and must upgrade their systems online, without constraining the live workload [6,22]. Industry best-practices recommend rolling upgrades, which upgrade-and-reboot each node in a wave rolling through the cluster [5,18].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

To upgrade or not to upgrade

Dumitraş

Narasimhan

Tilevich

2010

Proceedings of the ACM International Conference on Object Oriented Programming Systems Languages and Applications

View full text Add to dashboard Cite

Online software upgrades are often plagued by runtime behaviors that are poorly understood and difficult to ascertain. For example, the interactions among multiple versions of the software expose the system to race conditions that can introduce latent errors or data corruption. Moreover, industry trends suggest that online upgrades are currently needed in large-scale enterprise systems, which often span multiple administrative domains (e.g., Web 2.0 applications that rely on AJAX client-side code or systems that lease cloudcomputing resources). In such systems, the enterprise does not control all the tiers of the system and cannot coordinate the upgrade process, making existing techniques inadequate to prevent mixed-version races. In this paper, we present an analytical framework for impact assessment, which allows system administrators to directly compare the risk of following an online-upgrade plan with the risk of delaying or canceling the upgrade. We also describe an executable model that implements our formal impact assessment and enables a systematic approach for deciding whether an online upgrade is appropriate. Our model provides a method of last resort for avoiding undesirable program behaviors, in situations where mixed-version races cannot be avoided through other technical means.

show abstract