Whitepapers

The following papers provide a general introduction to publish-subscribe middleware focusing on DDS and comparing it with other middleware technologies and standards.

03/2009

10/2006

03/2005

  •  

    Designing and constructing Real-Time Distributed Industrial Vision Systems (RT-DIVS) from scratch is very complicated task. RT-DIVS has Conflicting requirements such as reasonable development cost, ease of use, reusable code and high performance. The success key in building such systems is to recognize the need for middleware software. Middleware plays a major role in developing distributed systems efficiently.

    Real-Time Publish-Subscribe (RTPS) model is one of the latest developments in Real-Time middleware technologies. Network Data Distribution Service (NDDS) is RTPS middleware developed by Real-Time Innovation (RTI). NDDS is widely used in Real-Time distributed and embedded systems for mission critical applications. The research work presented in this paper discusses the employment of NDDS for RT-DIVS and the advantages of NDDS’s Quality of Service (QoS) policies in covering the requirements of RTDIVS.

    An experimental test set-up is used to verify the NDDS’s performance for RT-DIVS. Tests results show that RTPS middleware (and NDDS specifically) is suitable for soft and firm timelines requirements for distributed industrial vision systems.

     

02/2007

  • Modern military satellite communications terminals have typically been built as multiprocessor systems. Because of increasing pressure for reuse and modularity, current programs have been encouraged to consider the use of component middleware. While Common Object Request Broker Architecture is the most mature middleware standard available, its invocation semantics present considerable challenges for the development of such systems. Through reasoning about quality attributes, we found that a real-time publish-subscribe middleware reduces coupling, improves composability, and reduces the risk of architectural mismatch, deadlock, and integration problems compared to an invocation based system. In building a communications-on-the-move (COTM) node, we found that this type of middleware, which exemplifies an implicit-invocation architectural style, promotes ease of system evolution and an incremental integration approach.

07/2008

11/2006

04/2006

04/2005