Imposing a memory management discipline on software deployment

Abstract

The deployment of software components frequently fails because dependencies on other components are not declared explicitly or are declared imprecisely. This results in an incomplete reproduction of the environment necessary for proper operation, or in interference between incompatible variants. In this paper we show that these deployment hazards are similar to pointer hazards in memory models of programming languages and can be countered by imposing a memory management discipline on software deployment. Based on this analysis we have developed a generic, platform and language independent, discipline for deployment that allows precise dependency verification; exact identification of component variants; computation of complete closures containing all components on which a component depends; maximal sharing of components between such closures; and concurrent installation of revisions and variants of components.We have implemented the approach in the Nix deployment system, and used it for the deployment of a large number of existing Linux packages. We compare its effectiveness to other deployment systems.

WebDSL: A Case Study in Domain-Specific Language Engineering

“…Thus, in the domain of web applications such a virtual machine would appear to run WebDSL applications directly, and behind the scenes generate the Java/XML implementation code, compile it, and activate the application server to run the application. The Nix software deployment system [39,37] provides a suitable infrastructure for realizing this scenario. Using a functional language, deployment configurations from source builds to service activation can be described [38].…”

“…The SDF syntax definition formalism [53,101], the Stratego/XT program transformation language and tool set [103,17,19], and the Nix deployment system [39,37] provide technology for defining languages and the tools needed for their operation. Publications resulting from this research typically present innovations in the technology, illustrated by means of case studies.…”

Automated Deployment of a Heterogeneous Service-Oriented System

“…To solve the complexities of the deployment process of distributed systems such as SDS2, we designed Disnix [8] (http://nixos.org/disnix), a distributed deployment extension to the Nix deployment system [9], [10].…”

Modelling Deployment Using Feature Descriptions and State Models for Component-Based Software Product Families

“…There are tools that can manage the lifecycle of components, such as Nix [6], the Software Dock [2], and Sofa [7]. These systems have downsides however.…”