The Design and Performance of a Scalable ORB Architecture for CORBA Asynchronous Messaging

Abstract

Historically, method-oriented middleware, such as Sun RPC, DCE, Java RMI, COM, and CORBA, has

Supporting component-based failover units in middleware for distributed real-time and embedded systems

“…A suitable mechanism is the CORBA Asynchronous Method Invocation (AMI) [20,21] specification. AMI allows the FaultCorrelationManager as a client to issue all shutdown requests without having to wait for their response in between, which would significantly reduce shutdown time, especially in large deployments.…”

RTZen: Highly Predictable, Real-Time Java Middleware for Distributed and Embedded Systems

“…During the last decade, a considerable amount of standardization [29] and research [30][31][32][33][34] work has been done on CORBA, and some results derived from this work have been incorporated in various ORBs available today, both commercial [35,36] and opensource [37,6,38].…”

Evaluating policies and mechanisms to support distributed real‐time applications with CORBA

“…The CORBA 2.4 standard [2] includes the Messaging [19] and Real-time CORBA specifications [18] that support many of these features. The Messaging specification defines asynchronous operation models [21] and a QoS framework that allows applications to control many end-to-end ORB policies. The Realtime CORBA specification defines interfaces and policies for managing ORB processing, communication, and memory resources.…”

“…An increasing number of research efforts are focusing on integrating QoS and real-time scheduling into middleware like CORBA. Our previous work on TAO has examined many dimensions of ORB middleware design, including static [5] and dynamic [28] operation scheduling, event processing [6], I/O subsystem [31] and pluggable protocol [32] integration, synchronous [22] and asynchronous [21] ORB Core architectures, IDL compiler features [38] and optimizations [1], systematic benchmarking of multiple ORBs [39], patterns for ORB extensibility [14] and ORB performance [15]. In this section, we compare our work on TAO with related QoS middleware integration research.…”