A framework for QoS-aware software components

Abstract

The next generation of software systems will be highly distributed, component-based, service-oriented, will need to operate in unattended mode and possibly in hostile environments, will be composed of a large number of "replaceable" components discoverable at run-time, and will have to run on a multitude of unknown and heterogeneous hardware and network platforms. This paper focuses on service oriented-architectures in which each component provides a set of interrelated services to other components. These components are QoS-aware (i.e., aware of Quality of Service requirements) and are capable of engaging in QoS negotiations with other components of a distributed application. The main contributions of this paper are: i) the description of an architecture for QoS-aware software components that are able to negotiate QoS requirements with other components, ii) the specification of the protocols used for QoS negotiation and admission control at the QoS-aware components, iii) a report on the implementation of a QoS-aware component, and iv) the experimental validation of the ideas presented in the paper.

Performance model driven QoS guarantees and optimization in clouds

“…The models used by the application administrator may be simple feedback loops such as load balancing, or may take advantage of a performance model as described in [13] [20], with decisions limited in scope to the one application and the resources provided to it. By itself this level may not have sufficient capability to assure QoS.…”

Fast scalable optimization to configure service systems having cost and quality of service constraints

“…For example, Beaty et al [1] proposed a heuristic approach to optimizing server migration and consolidation in terms of performance level. Menasce et al [15][16] describe heuristics for good combinations of QoS-aware components or service information providers across networks. Their work is limited by using queueing models which ignore contention for software resources.…”

QoS management in service-oriented architectures

“…Other models such as the Layered Queuing Network (QN) model could be used [35]. In our previous work [26], we had only accounted for hardware contention in our performance models. In the current work, we use a combination of a software queuing network (SQN) and a hardware queuing network (HQN) as illustrated in Fig.…”