Architectural support for quality of service for CORBA objects

Abstract

CORBA is a commercial standard for distributed object computing which shows great promise in the development of distributed programs. Its interface description language (IDL) enables objects to be developed independently of the underlying programming language, operating system, or computer architecture on which they will execute. Programs deployed in a wide-area distributed system encounter conditions which are much more hostile and varying than those operating in a single address space or within a single local area network. In this paper we discuss four major problems we have observed in our developing and deploying wide-area distributed object applications and middleware. First, most programs are developed ignoring the variable wide area conditions. Second, when they do try to handle these conditions, application programmers have great difficulty because they are different from the local objects they are used to dealing with. Third, IDL hides information about the tradeoffs any implementation of an object must make. Fourth, there is presently no way to systematically reuse current technology components which deal with these conditions, so code sharing becomes impractical.In this paper we also describe our architecture, Quality of Service for CORBA Objects (QuO), which we have developed to overcome these limitations and integrate their solution by providing QoS abstractions to CORBA objects. First, it makes these conditions first class entities and integrates knowledge of them over time, space, and source. Second, it reduces their variance by masking. Third, it exposes key design decisions of an object's implementation and how it will be used. Fourth, it supports reuse of various architectural components and automatically generates others.This work is sponsored by Rome Lab.

Simplifying autonomic enterprise Java Bean applications via model-driven engineering and simulation

“…QuO [36] is another middleware architecture for mapping QoS to objects. In QuO, the state of the operating environment can be partitioned into regions.…”

Q-SCA: Incorporating QoS support into software communications architecture for SDR waveform processing

“…Such examples include 2K Q (Nahrstedt et al, 2000), Agilos (Li and Nahrstedt, 1999), TAO (Kuhns et al, 2000), and QuO (Zinky et al, 1997). Each of them provides a method for application programmers to describe QoS requirements along with a mechanism for enforcing those requirements.…”

Extensible soft semantic web services agent

“…Garvin [8] associates eight dimensions with quality, including performance and reliability. Software systems quality of service has been extensively studied in [9,11,26]. For middleware systems, Frlund and Koisinen [7] present a set of practical dimensions for distributed object systems reliability and performance, which include time to repair (TTR), time to failure (TTF), availability, failure masking, and server failure.…”

“…As a consequence, it is not flexible to use classical mathematical modeling methods to evaluate the QoS of semantic Web services. Although there are several existing QoS models [3,[7][8][9]11,17,18,21,26], none of them are suitable for the requirements considered in this paper. These QoS models are based on precise QoS metrics and specific application domains.…”