Data Distribution Service: Difference between revisions

Revision as of 10:44, 24 June 2020

Revision as of 11:49, 24 June 2020

Line 18:

* what happens if messages cannot be delivered

DDS allows the user to specify [[quality of service]] (QoS) parameters to configure discovery and behavior mechanisms up-front. By exchanging messages anonymously, DDS simplifies distributed applications and encourages modular, well-structured programs. <ref>{{cite web |url=https://www.slideshare.net/Angelo.Corsaro/the-data-distribution-service-tutorial |title=The DDS Tutorial |last=Corsaro |first=Angelo |website=Slidesharecitation needed|date=May 27,October 20142019}}</ref>

DDS also automatically handles hot-swapping redundant publishers if the primary fails. {{citation needed|date=October 2019}} Subscribers always get the sample with the highest priority whose data is still valid (that is, whose publisher-specified validity period has not expired). It automatically switches back to the primary when it recovers, too.

Line 64 ⟶ 63:

Starting with DDS version 1.4 in 2015, the optional DLRL layer was moved to a separate specification.<ref>{{Cite web |title= DDS Data Local Reconstruction Layer (DDS-DLRL) |date= April 2015 |url= http://www.omg.org/spec/DDS-DLRL/ |accessdate= November 9, 2016 }}</ref>

== Open Source ==

In the past few years few Open Source implementations of DDS have come to life. The two most active projects being:

* [[Eclipse Cyclone DDS]] [http://github.com/eclipse-cyclonedds/cyclonedds]

* [[FastRTPS]] [https://github.com/eProsima/Fast-DDS]

== See also ==