This paper describes the problems DDS data-centric messaging technology was designed to address, including flexible deployment, performance and scalability, robust architecture, and secure communication. It was written from the perspective of a US Navy user, but the problems and solutions it describes are not specific to that environment.

A new class of distributed systems are beginning to employ DDS technology. These systems are characterized by broad geographic distribution, high aggregate data volumes, and narrow data interest within any particular node or local application. This presentation describes a set of enhancements to DDS and DDS-RTPS to better support such systems, in particular in the areas of data filtering and service discovery.

Approaches and techniques to integrating large-scale systems and systems of systems.

Analysis of the requirements of these systems and how specific features of DDS  can be leveraged to integrate these large systems. 

This presentation provides an overview of the benefits and functionality of the DDS specification. It was given to a plenary session of the Robotics Task Force at the OMG technical meeting in Long Beach, CA.

This presentation is a summary of the revised RTI/PrismTech joint submission to the "Extensible and Dynamic Topic Types for DDS" RFP. It was given to a plenary session of the Middleware And Related Services (MARS) Task Force of the OMG at the technical meeting in Long Beach, CA.

The existing Java API for DDS, which is derived from the IDL PSM (Platform-Specific Model), limits cross-vendor portability and performance. It also fails to take advantage of libraries and facilities unique to the Java platform, such as generic types and built-in serialization support. The proposed RFP (which was later issued with document number mars/09-12-16) asks submitters to propose an improved Java API to remove those limitations.

The DDS and JMS specifications offer alternative visions of publish-subscribe communication and have traditionally been deployed in different capacities; DDS provides a data distribution model based on strong typing and flexible QoS-based control over data delivery, while JMS provides a traditional messaging model based on loosely structured data and emphasizes a simple and portable programming model.

The Impact of a Real-Time JVM on Middleware Performance: Lessons Learned from Implementing DDS on IBM’s J9, Presentation given by Ken Brophy and Rick Warren, RTI, at the 2007 Real-Time and Embedded Systems Workshop