RTI Data Distribution Service

Decentralized Peer-to-Peer Architecture for High Performance, Scalability and Robustness

RTI Data Distribution Service employs a novel, completely decentralized run-time architecture. Applications directly communicate with each other in a true peer-to-peer manner. Messages are not routed through any intermediate broker, server or daemon processes as they are with other Enterprise Service Bus (ESB), enterprise messaging and DDS implementations.

RTI's integrated discovery capability automatically establishes the peer-to-peer data flows between applications at run-time. No external directory service is required.

Benefits

• Minimizes latency and maximizes determinism — eliminates major contributors to latency and jitter: gratuitous message hops and task switches
• Maximizes system-wide throughput and scalability
• Eliminates bottlenecks and choke points: aggregate throughput is limited only by the capacity of the network infrastructure, not by the capacity of a broker, server or daemon
• Latency remains consistently low even as throughput increases since messages do not have to be queued in a broker or daemon
• Eliminates any single point of failure or security vulnerability — there is no common point through which all messages pass on either a system-wide or per-node basis
• Supports deployments in which servers are unfeasible — for example, ad hoc tactical environments
• Eases embedding — applications are completely self-contained and do not depend on the installation or administration of any external software
• Reduces IT costs
• Eliminates servers and the requirement to administer and scale a heavyweight and centralized integration infrastructure
• Cuts network overhead at least in half since messages are sent once—directly to their recipient—rather than being relayed by a broker

Integrating Disparate Systems

RTI's peer-to-peer architecture accommodates integrating disparate systems, including those that span multiple networks and incorporate other native integration technologies.

Integrating Applications across Networks

RTI supports two approaches for integrating applications that use different transport protocols (such as UDPv4 and UDPv6) or run over different networks:

• Applications can concurrently participate as peers on multiple networks.
• RTI Routing Service can be used to bridge between transports and networks. (Applications on the same network still communicate peer-to-peer.)

Integrating non-RTI Applications

RTI Data Distribution Service retains peer-to-peer semantics even when integrating applications that do not natively use RTI middleware for communication.

• RTI Data Distribution Service applications can directly communicate with systems integrated using other RTPS compliant DDS implementations. (Since other DDS implementations are not peer-to-peer, messages they produce or consume will route through their broker, daemon and/or network service. This will not affect messages flowing between applications that directly use RTI Data Distribution Service.)
• RTI's adapters to other standards and applications (e.g., Web Services, SOAP, REST and relational databases) are completely decentralized. Any number of instances of each adapter can run anywhere on the network, for example, as a shared service or as a bridge on the same node as an application being integrated.