This document discusses Data Distribution Service (DDS) as an industrial Internet of Things connectivity framework. It compares message-centric and data-centric architectures, noting that DDS takes a data-centric approach. The document then provides an overview of DDS, describing its core functions like discovery, evolution, load balancing and quality of service policies. It demonstrates DDS through examples of backward compatibility, redundancy, and integration with other tools. DDS creates a shared data bus that allows systems to evolve over time while maintaining consistency.

1. Data Distribution Service (DDS)
A Connectivity Framework for Distributed Systems
Gal Schlesinger November 18

2. An Alternative Approach
to Distributed Systems Design…
• How do you discover remote services?
• How do you manage messages/services evolution?
• How do you manage load balance messages?

3. Message Centric VS Data Centric
Architecture Approach

4. Message Centric VS Data Centric Design
• Distributed systems work by sending information
between independent modules.
• How to get the right information from the right
producers to the right consumers at the right time, is
perhaps the first and most important design
consideration of any distributed systems.
• Distributed systems must also share and manage the
state of each one of the above.

5. Message Centric VS Data Centric Design

6. The Database Analogy
• Before databases, storage systems were files with application-
defined structure.
• The database arose as a data-centric infrastructure technology
that provides one key benefit: a source of consistent truth.

7. Message Centric VS Data Centric Design
• Choosing the right paradigm deserves careful thought.
– How important is controlled state?
– How challenging is integration?
– What is your project lifecycle?
• It is not a black and white situation,
you can incorporate both approaches
in your design.

8. Data Distribution Service (DDS)
The Industrial IOT Connectivity
Framework & Architecture

9. What most systems of systems look like
What happens
to the system
when your
needs evolve
How the system is initially designed

10. RTI DDS Data Bus
DDS Creates This…
What happens
to the system
when your
needs evolve
RTI DDS Data Bus

11. What is DDS?
DDS – Data Distribution Service
• Application Programming
Interface (API) Library
• Middleware Protocol
– Managed by Object Management
Group (OMG)

12. Connectivity Framework Core Functions

13. DDS Live Demo

14. From an Interactive Data Language (IDL) to an Executable

15. Basic DDS QOS Demo
DURABILITY USER DATA
HISTORY TOPIC DATA
READER DATA LIFECYCLE GROUP DATA
WRITER DATA LIFECYCLE PARTITION
LIFESPAN PRESENTATION
ENTITY FACTORY DESTINATION ORDER
RESOURCE LIMITS OWNERSHIP
RELIABILITY OWNERSHIP STRENGTH
TIME BASED FILTER LIVELINESS
DEADLINE LATENCY BUDGET
CONTENT FILTERS TRANSPORT PRIORITY

16. Backward and Forward Compatibility
using DDS Extensible Types

17. System Redundancy
Using DDS Ownership QOS

18. Excel & DDS Integration

20. RTI DDS Connext Family

21. 18-Nov-18© 2012 RTI • COMPANY CONFIDENTIAL38

22. Questions?

23. Gal Schlesinger | Connext DDS Field Application Engineer
Galsc@matrix.co.il | Mobile: +972-50-7856567
Thank You