How different messaging semantics can affect SCA applications performances: a benchmark comparison

Abstract

Software Communications Architecture (SCA) compliant radios typically contain a large number of software components. Some software components provide access to hardware devices while others perform signal processing. By interacting with each other, the software components implement a radio communications standard. To interact, the software components use a middleware called Common Object Request Broker Architecture (CORBA). Using CORBA, each interaction is carried out as an exchange of messages between two components. CORBA supports two main types of messaging: one-way and two-way. This article explores the differences between the two types of messaging and provides performance metrics. The article also describes design approaches that can be used to avoid common pitfalls associated with the use of both types of messaging.