Runtime software reorganization by traditional OS features

With the increased complexity of software and requirements for non-stop service features, it is important to establish an effective method for online or runtime program updating. For commercial servers, even a short break of service can cause a great loss for a company, and modern complex software systems are frequently updated for patching security holes or adding new features. To cope with such situations, a new paradigm for easy and effective software maintenance is needed. Many approaches have been proposed in software engineering for autonomous evolution or growth schemes, while in the domain of computer hardware or traditional machines, the in-operation replacement of parts (known as a “hot swap”), where a defective module in a complex system can be replaced during its operation, is common. In this paper, we discuss such a “hot swap” method for the software system, as well as ways to divide the whole system into basic modules and to reorganize them. We focus on methods using facilities that are available in traditional UNIX-type operating systems, such as dynamic linking or process management. With experiments on prototype routines, we demonstrate the feasibility of such a technique, which employs a version manager routine included in a simple example application