Difference between RTI DDS and RTI JMS ????

2 posts / 0 new
Last post
Last seen: 6 years 2 months ago
Joined: 04/08/2013
Posts: 6
Difference between RTI DDS and RTI JMS ????


As the RTI has implement JMS specification , so how  RTI-JMS differ from RTI-DDS?

And, If I want to implement BitTorrent over p-s middleware. Which of the two techniques is better???

Thank you ,

Edwin de Jong's picture
Last seen: 6 years 2 months ago
Joined: 05/06/2013
Posts: 2

RTI offers both DDS and JMS as interfaces to our publish-subscribe middleware. To a limited extent the choice of using DDS or JMS comes down to personal preference: are you more familiar and experienced with the one or the other. Note that since RTI middleware is publish-subscribe, the point-to-point domain (queues) is not supported by our JMS interface.

However, a key advantage of DDS is that it incorporates both messaging and data caching to deliver on the demanding requirements of distributed real-time applications. In general consider using DDS if your application is well served by typed interfaces, maximized throughput and minimal latency,  compact on-the-wire data representation, high-performance content and time-based filtering, and detailed control over real-time Quality-of-Service. Unlike JMS, RTI's DDS implementation is available not only in Java but also in several other languages, including C/C++ and C#, and interoperates seamlessly across these languages. In addition, the DDS interface is supported on a wide variety of platforms, including embedded hardware running real-time operating systems.