DDS is the industrial-grade messaging layer under ROS 2 — a decentralized, real-time publish–subscribe system with no central master, built-in discovery, and configurable reliability, which is what makes ROS 2 fit for production robots.
DDS is the plumbing under ROS 2 that actually moves messages between programs. It's a proven, industrial system with no central hub, automatic discovery of who's talking, and knobs to trade speed for reliability.
The biggest change from ROS 1 to ROS 2 isn't visible in your code — it's the plumbing underneath. ROS 2 replaced its custom transport with DDS, and that decision is why ROS 2 is trusted on real, production robots.
What it is
DDS (Data Distribution Service) is a mature, standardized publish–subscribe middleware — the layer that actually carries messages between programs. It comes from aerospace and defense, where it's run mission-critical systems for two decades. ROS 2 sits on top of it: when your nodes exchange messages on topics, DDS is doing the real work of delivering them.
ROS 2 rides on DDS
Your ROS code talks to a client library, which talks to DDS, which handles discovery, delivery, and reliability across the network.
What it gives ROS 2
No master. ROS 1 needed a central master to connect nodes — a single point of failure. DDS uses peer-to-peer discovery: nodes find each other automatically, so any node can come and go independently.
Quality of Service. DDS lets each stream be tuned — reliable vs best-effort, keep-last vs keep-all, deadlines and liveliness — so a robot can prioritize a control command over a video frame.
Real-time capable. With the right DDS implementation, ROS 2 can meet real-time deadlines.
Security. DDS-Security adds authentication and encryption, built in rather than bolted on.
Native multi-robot. Domain IDs partition the network, so fleets coexist cleanly.
The trade-offs
DDS is powerful but adds complexity: there are multiple vendor implementations (Fast DDS, Cyclone DDS), discovery can flood large networks, and its QoS knobs are the very thing that trip up beginners when a publisher and subscriber silently fail to connect. ROS 2 abstracts most of it, but a serious deployment still tunes the DDS layer.
Why it matters
DDS is the foundation that turned ROS from a research tool into production-capable robotics middleware. Understanding that ROS 2 is DDS underneath explains its biggest strengths — decentralization, real-time, security — and its quirks.
