Vortex OpenSplice has proven scalability in the most demanding mission and business critical applications. Vortex OpenSplice uniquely offers users the ability to have a Shared-Memory (Federated) option for scalability or a Standalone (Single-Process) option for usability.

Vortex OpenSplice Architecture - Federated and Standalone Deployment

To take advantage of modern computing architectures, it has become increasingly more important to be able to exploit multicores. Vortex OpenSplice provides a shared-memory deployment option that facilitates a federated architecture by offering ultra-low latency inter-core communication along with maximal nodal scalability. Vortex OpenSplice also provides the default Standalone deployment option for environments where shared memory is unavailable or undesirable.

Vortex OpenSplice Architecture Federated Standalone scalability

Recognizing the difficulty of choosing the right architecture upfront in the system design and development cycle, Vortex OpenSplice allows you to run exactly the same application, meaning the same executable, in different architectural styles by simply changing a runtime parameter. This makes Vortex OpenSplice the only Data Distribution Service (DDS) middleware implementation that gives you the choice of selecting, as well as easily adapting, the deployment architecture that best suits you.

Shared-Memory (Federated) Scalability:

When configuring Vortex OpenSplice for the Federated deployment architecture, data is physically present only once on a machine’s federation, and smart administration still provides each subscriber within the federation with his own private 'view' on this data. This allows a reader’s data cache to be perceived as an individual 'database' that can content-filtered, queried, etc. (using the content-subscription profile as supported by the Vortex OpenSplice core). The shared-memory architecture results in an extremely low footprint, excellent scalability and optimal performance when compared to other DDS implementations where each reader/writer are ‘communication-endpoints’ each with their own storage (i.e. historical data both at reader and writer) and where the data itself still has to be moved, even within the same platform.

Further information about Scalability Benchmarks is available here.

Standalone (Single-Process) Usability:

This deployment allows the DDS applications and Vortex OpenSplice middleware libraries to be simply linked together into a single operating process. One of the advantages of this deployment option is that, there is no need to pre-configure a shared memory segment as dynamic heap memory is utilized by the standalone process. Apart from this 'zero-configuration' advantage, there's also no need to start up the federation's services as all functionality is 'bundled' within the application process. The middleware's lifecycle and with that, the lifecycle of the information is 'simply coupled' to that of the application. Standalone/Single Process deployment is the default architecture provided within Vortex OpenSplice and allows for easy deployment with minimal configuration required for a running DDS system.