Data Distribution Service (DDS) Middleware is an OMG-standardised publish-subscribe communication middleware designed for real-time, scalable, and decentralised data exchange in safety-critical and high-performance distributed systems. It defines a Data-Centric Publish-Subscribe (DCPS) model in which participants discover each other automatically and exchange typed data via a global data space, governed by a rich set of Quality of Service (QoS) policies covering reliability, latency, deadline, liveliness, and durability. DDS is the foundational communication layer for ROS 2, NATO’s STANAG 4910 tactical networks, and aerospace control systems.
Content
- DDS was standardised by the Object Management Group (OMG) in 2003 following work at Real-Time Innovations (RTI) and other vendors in the late 1990s. The core motivation was the inadequacy of client-server and broker-based middleware (CORBA, SOAP) for embedded real-time systems where a central broker creates a single point of failure and adds unacceptable latency. DDS introduces a fully decentralised, peer-to-peer data model: publishers write data to named Topics; subscribers declare interest in Topics; the middleware handles discovery and delivery without a central broker. The specification defines the DCPS (Data-Centric Publish-Subscribe) API and the RTPS (Real-Time Publish-Subscribe) wire protocol, enabling interoperability across vendor implementations.
- The DDS QoS policy framework is its defining differentiator. Over 20 distinct QoS policies govern data exchange: RELIABILITY (best-effort vs. reliable), DEADLINE (maximum acceptable data age), LATENCY_BUDGET, LIVELINESS (automatic detection of failed participants), DURABILITY (late-joining subscriber receives historical data), HISTORY (depth of sample cache), OWNERSHIP (exclusive vs. shared write access), and PARTITION (logical namespace isolation). This policy set allows system designers to express application-level requirements declaratively, with the middleware enforcing them automatically. Automatic discovery uses SPDP (Simple Participant Discovery Protocol) and SEDP (Simple Endpoint Discovery Protocol) over multicast, eliminating manual configuration.
- DDS became the communication backbone of ROS 2 (Robot Operating System 2), released in 2017 as a complete redesign of ROS 1 to address real-time and production deployment shortcomings. ROS 2’s rmw (ROS middleware) abstraction layer supports multiple DDS implementations—FastDDS (eProsima, default), Cyclone DDS (Eclipse), RTI Connext, and GurumDDS—providing vendor portability. Beyond robotics, DDS is mandated in multiple defence and aerospace standards: the US DoD’s FACE (Future Airborne Capability Environment) technical standard, NATO’s STANAG 4910 for UAS communications, and air traffic management systems. Medical device interoperability profiles (OpenICE) also use DDS for physiological data distribution in operating theatre environments.
- Through 2024–2025, DDS adoption continues to expand with the growth of autonomous vehicles, drone swarms, and smart manufacturing. The OMG DDS Security specification (DDS-Security) adds authentication, authorisation, and encryption plugins to the wire protocol, addressing the attack surface of safety-critical real-time networks. ROS 2 Jazzy Jalisco (2024 LTS release) further matures the DDS abstraction, and micro-ROS extends DDS connectivity to microcontrollers using Micro XRCE-DDS. Integration with time-sensitive networking (TSN) Ethernet hardware is an active standardisation area, coupling DDS’s logical QoS policies with Layer 2 scheduling guarantees for deterministic industrial network fabrics.