Semantics of a runtime adaptable transaction manager

Abstract

Database Management Systems (DBMSs) that can be tailored to specific requirements offer the potential to improve reliability and maintainability and simultaneously the ability to reduce the footprint of the code base. If the requirements of an application change during runtime the DBMS should be adapted without a shutdown. Runtimeadaptation is a new and promising research direction to dynamically change the behavior of a DBMS. Especially the adaptation of the Transaction Manager (TM) states a challenge.In this paper, we present the session semantics of a runtimeadaptable TM. We define preliminaries and assumptions to activate the TM during sessions from a conceptual point of view. The advantages and disadvanteges of different approaches are discussed, especially regarding the occurence of ANSI SQL phenomena. From a technical point of view, we define requirements for the architecture of the TM and the DBMS that arose in our prototype.

Dynamic Metamodel Extension Modules to Support Adaptive Data Management

“…The authors experimented with two methods of enabling dynamic adaptation, namely dynamic aspect-oriented programming (d-AOP) and a second approach where a component implementation, or part of it, is exchanged in order to adapt the component while the interface remains valid. In [8], they present how a Transaction Manager can be added and removed at run-time using the d-APO approach which the authors argue in [7] has several disadvantages in terms of performance, code maintenance, limited functionality and testing. Therefore the approach of component replacement has been adopted in the CoRBA framework.…”