Talk:Data Distribution Service

Other publish/subscribe systems
i haven't understood the difference between OMG's Data Distribution Service and other publish/subscribe system, such as gryphon, siena, adn so on.

who can give a survey of comparing DDS and other pub/sub middleware?

thanks.


 * DDS is standard, the others (Siena, Mercury, Spread etc) are not. NDDS is an commercial implementation of DDS used by Department of Defense and others. The QoS part is also important.

The question is larger than simply that one (OMG DDS) is a standard and the others are not. Publish-Subscribe comes in various 'flavors' (Topic-based, Content-based, Type-based) and within them various ways to implement each. OMG DDS is based on the "Data-Centric Publish Subscribe" model where, in order to make it amenable for use in embedded and/or real-time environments, Topics are defined in accordance with a data model (think relational) and associated in various clearly defined ways with a Quality of Service (QoS). These QoS attributes define the offered (or expected) behavior of a publication (or subscription).

Note that the product from RTI is no longer called NDDS but "RTI DDS"; the name "NDDS" is reserved for their product that pre-dates (but which helped form the basis of, along with THALES SPLICE) the OMG DDS spec. —Preceding unsigned comment added by 128.29.43.2 (talk) 15:16, 6 June 2008 (UTC)

The answer is somewhat misleading, HLA (High Level Architecture) is an IEEE standard for a Publish/Subscribe middleware too. There are differences between HLA and DDS, but they are not particularly significant. HLA is targeted more towards the Modeling and Simulation community, while DDS is targeted towards a broader community. Careful examination will show that HLA can do things that DDS can't, and DDS can do things that HLA can't. However, missing features on both sides can be added by users by changes to the object model. --63.139.25.250 (talk) 13:54, 4 March 2009 (UTC)


 * One of the notable absences is Asian company "DDS" products. Rather than me listing some that I know about, perhaps the Asian DDS community should be solicited to add their content. 2001:558:6017:18E:DD02:57C1:43CD:4CEF (talk) 18:12, 23 January 2023 (UTC)

These words
''Data Distribution Service for Real-time Systems (DDS) is a specification of a publish/subscribe middleware for distributed systems created in response to the need to standardize a data-centric publish-subscribe programming model for distributed systems. ''
 * Data-centric? Programming model? Please explain. Thanks, --Abdull (talk) 19:25, 24 August 2008 (UTC)
 * @Abdull not node/machine/hardware centric. 203.6.69.2 (talk) 01:51, 26 February 2021 (UTC)

Marshalling vs. Serialization
The phrare "marshalling and demarshalling" links to the page "serialization".

Wikipedia defines marshalling as similar but different from serialization. http://en.wikipedia.org/wiki/Marshalling_(computer_science)

Needs to be resolved — Preceding unsigned comment added by 207.107.233.124 (talk) 19:11, 30 June 2011 (UTC)

History
The recent edit by MrOllie I believe is incorrect, the original shows where the created product exists today. — Preceding unsigned comment added by ChrisLloydPT (talk • contribs) 16:09, 31 October 2012 (UTC)
 * The history section is about who created the standard, not about their products or what companies currently have business interests in them. - MrOllie (talk) 16:22, 31 October 2012 (UTC)
 * The History section is misleading from its very first sentences, by erroneously conflating two uses of the word "specification." There is an international DDS standard specification which was created by the OMG and its member companies, not solely by any one company/team of companies. Multiple corporate and non-corporate member parties participated in that process. A pair of them contributed much more to the DDS standard than the other parties did, because they had previously been working on such a commercial product (as noted), and the other parties respected that work. Readers of this article are thus unknowingly exposed either to corporate marketing information, or to inadvertently misleading English. 2001:558:6017:18E:DD02:57C1:43CD:4CEF (talk) 18:41, 23 January 2023 (UTC)

Merge and move?
Real-Time Publish-Subscribe (RTPS) Protocol is a badly-named article that has never had any independent sources, so does not meet notability guidelines. It needs to be either deleted or merged to this one. We generally do not have separate articles on system and their protocols unless they are independently notable and each meet requires for a stand-alone non-stub article. I vote merge here and remove the duplication and wordiness. Also this one seems to describe one particular data distribution service, not the general concept. So should have been kept in upper case. English capitalizes proper nouns. Publish–subscribe pattern is probably the closest to the generic concept. W Nowicki (talk) 17:35, 8 November 2013 (UTC)


 * Merge, for the arguments given above.67.198.37.16 (talk) 23:17, 26 September 2015 (UTC)
 * ✅ Sorry it took so long. This article also needed some work. See how much I can get done today. Thanks for your patience. W Nowicki (talk) 23:08, 9 November 2016 (UTC)

Requested move

 * The following discussion is an archived discussion of the proposal. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section. 

The result of the proposal was moved. --BDD (talk) 18:13, 19 November 2013 (UTC)

Data distribution service → Data Distribution Service – This seems to describe one data distribution service in particular, the one specified by OMG. The general concept is covered elsewhere as described above. W Nowicki (talk) 17:38, 8 November 2013 (UTC)
 * The above discussion is preserved as an archive of the proposal. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.