Connectivity Framework Annex A: Assessment Template: DDS
A. 6.5 Implementation Viewpoint A. 6.5.4 Scalability Considerations
Data Objects( Section 4.2.4.1)
Apps( Section 4.2.4.2)
A. 6.5.5 Availability Considerations
Redundancy( Section 4.2.5.1)
Recovery( Section 4.2.5.2)
A. 6.5.6 Deployment Considerations
Platforms Constraints( Section 4.2.6.1)
Incremental Upgrades
( Section 4.2.6.2)
Can the connectivity framework effectively handle an increasing number of data objects? What limits data object size?
Yes, DDS can handle an effectively increasing number of data objects. Every data object is identified by a GUID— the number of unique GUIDs limits the number of data objects in a domain. The port numbers available on a host limits the number of domains.
There is no theoretical limit on the data object size. In practice, it will be limited by the amount of memory available on a host.
Can the connectivity framework effectively support interface evolution for an increasing number of distributed application components?
Yes, DDS can effectively support interface evolution for an increasing number of distributed application components. Application components are loosely coupled— they interact with the data, not with each other; thus, the interfaces are data-oriented and can evolve independently. The data types in a data-oriented interface can also evolve through extension or mutation— the rules are defined in the DDS-XTypes v1.1 specification.
Can the connectivity framework support continuous availability over a defined systemrelevant time period?
Yes, DDS can support continuous availability over a defined system relevant time period. DDS accomplishes this by having a continuous ongoing automatic discovery, so that components can be added or removed at any time, and by providing an optional DDS- Persistence Service to cache the data outside of specific application components. Can the connectivity framework support recovery when fault conditions occur?
Yes, DDS can support recovery when fault conditions occur. It accomplishes this by signaling exceptions the application layer, by allowing application to change certain QoS policies, and by providing access to the automatic discovery data.
Does the connectivity framework support the operating system( OS), the CPU and the resource constraints on the platform( s) being used?
Yes, DDS implementations are available for most commonly used operating system and CPUs. DDS implementation can run on devices with limited memory resources(< 100kB). Does the connectivity framework facilitate incremental upgrades?
Yes, DDS can support incremental upgrades. DDS accomplishes this by means of automatic ongoing discovery when components are added or removed, data-oriented interfaces and support for data type evolution over a system’ s lifecycle.
IIC: PUB: G5: V1.0: PB: 20170228- 70-