Accelerating Time-to-Market
provided in different programming languages allowing applications to exchange information across operating systems , languages , and processor architectures . Low-level details like data wire format , discovery , connections , reliability , protocols , transport selection , QoS , security , etc . are managed by the middleware .
Instead of creating brittle , point-to-point network dependencies , DDS communicates over the concept of topics . Applications simply declare what kind of data or topics ( each topic has a welldefined data structure ) they are interested in , and DDS delivers it . This eliminates the brittleness of requiring applications to identify specific endpoints that they need to talk to – DDS handles all of this , so developers can focus on application code and not on how to send data over the network .
DDS Security is unique because it provides Network Layer 4 fine-grained read / write access control to the data . This is in contrast to Layer 2 / 3 all-or-none options , including IPSec , MACSec , and D / TLS ; these coarse-grained security alternatives expose more opportunities for exploitation . Using DDS fine-grained access control guarantees that only authorized applications can send and receive specific types of data over dedicated logical network partitions – enabling highly customizable communications supporting multiple security domains . This is softwaredefined security which is controlled through signed configuration files associated with each application .
DDS is loosely coupled and by using the concept of topics to communicate , it supports locationindependent processing . This promotes system modularity and resilience , which are key requirements for modular open system architecture ( MOSA ) systems . DDS is also platform agnostic . This enables transparent interoperability between DDS applications independent of programming language , hardware , and operating system .
In the previous section we presented a description of a high assurance software stack built on seL4 and DDS , and we explained several of its benefits when developing critical systems . We made the case about why it provides a compelling foundation . In the section , we discuss a reference implementation of this stack that we assembled using implementations of CAmkES from Hensoldt ( TRENTOS ®) and DDS from RTI ( Connext ®), respectively . TRENTOS is the only production ready implementation of CAmkES . Connext is the only DDS implementation certified to the highest levels for both flight safety and automotive systems . We then present multiple example architectures and discuss design trade-offs .
We start by presenting a brief description of Hensoldt ’ s commercial implementation of CAmkES , followed by RTI ’ s commercial implementation of DDS .
94 July 2022