A broker that bridges resource-constrained devices (Micro XRCE-DDS Clients) with the DDS global dataspace using the DDS-XRCE protocol.
Micro XRCE-DDS Agent is a broker that implements the DDS-XRCE protocol to allow resource-constrained devices, such as microcontrollers, to communicate with DDS (Data Distribution Service) networks. It acts as an intermediary, processing client requests for publishing, subscribing, and remote procedure calls, enabling these lightweight devices to participate in distributed systems as full DDS actors. This solves the problem of integrating extremely resource-constrained environments into larger, standards-based DDS ecosystems.
Embedded systems engineers and developers working on IoT, robotics, or industrial automation projects that require communication between microcontrollers and DDS-based distributed systems. It is also suitable for organizations using DDS who need to extend connectivity to resource-limited edge devices.
Developers choose Micro XRCE-DDS Agent because it provides a standards-compliant, lightweight bridge to DDS for constrained devices, supporting multiple transports and remote procedure calls. Its unique selling point is full adherence to OMG DDS-XRCE and DDS-RPC standards, ensuring interoperability while minimizing resource usage on clients.
Micro XRCE-DDS Agent respository. Looking for commercial support? Contact info@eprosima.com
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Implements OMG DDS-XRCE and DDS-RPC standards, ensuring seamless integration with existing DDS ecosystems, as highlighted in the README's emphasis on OMG specifications.
Supports built-in transports like UDPv4, UDPv6, TCPv4, TCPv6, Serial, and custom user-defined transports, providing flexibility for various network environments, per the README.
Enables resource-constrained devices like microcontrollers to act as DDS participants through lightweight clients, bridging the gap to larger distributed systems, as described in the architecture.
Available as a standalone executable, Snap package, or Docker image, simplifying deployment across different environments, as noted in the README's installation options.
The agent acts as a middleman, adding processing overhead and potential latency compared to direct DDS communication, which may impact performance-critical applications.
While built-in transports are supported, implementing custom transports or non-standard integrations requires additional development effort, as hinted in the README's mention of user-defined transports.
Tightly coupled with DDS standards, making it unsuitable for projects outside the DDS domain or those considering alternative middleware, limiting its versatility.