ZeroDDS tests a Rust DDS path for ROS 2

Zero Objects published v1.0.0-rc.3 of ZeroDDS on June 19, a Rust-based open source implementation of DDS. DDS, short for Data Distribution Service, is a real-time communication standard widely used in distributed systems and in ROS 2, where it acts as a transport layer between nodes, sensors and actuators. The news is not a visible robot, but a piece of robotics plumbing: the GitHub release ships installers and archives for multiple platforms, including artifacts named rmw-zerodds-shim, meant to connect this DDS stack to the ROS 2 middleware model.

The technical choice is the useful part. ROS 2 already works with several DDS middlewares, such as Cyclone DDS, Fast DDS or Connext depending on the deployment. ZeroDDS proposes another route: a Rust foundation, using a language valued for memory-safety properties and for reducing some classes of errors common in C and C++ systems code. In robotics, that can matter even when it is not visible in a demo. Middleware does not plan a path or detect an object, but it carries the messages used by perception, control and supervision. When that layer stalls, drops traffic or behaves differently across machines, the whole robot becomes harder to debug.

Caution is part of the story. The repository still says ZeroDDS is waiting for an OMG-assigned vendor ID. In practice, that means the project may claim wire compatibility with established DDS stacks, but it does not yet present that part as cleared for production cross-vendor deployments. The published version is also a release candidate, not a final stable release. For Mindshot, this is exactly why the item is worth a brief rather than a larger article: the signal is concrete enough to track, but not mature enough to describe as proven industrial adoption.

The short-term impact is mainly for teams experimenting with ROS 2 architectures, distributed simulation, or communication-heavy robotic systems. They can now evaluate a Rust DDS option, test its behavior under their quality-of-service profiles, and see whether the RMW integration holds up in their own workloads. RMW is the interface that lets ROS 2 switch middleware implementations without rewriting the application. If ZeroDDS clears the remaining steps, it will add one more option to a decision that is often underestimated: the reliability of the software bus that lets the parts of a robot talk to each other.