While being a simple local service, Viinex 2.0 is capable of participation in a distributed video management system. Out of the box, Viinex 2.0 contains built-in replication modules, which allow for eventual synchronization of video archives between Viinex 2.0 instances. There are also certain properties of Viinex 2.0 configuration which helps scaling up the embedding software which uses Viinex 2.0.
Arrange the data flow as required
Replication modules are available in Viinex 2.0 to arrange an arbitrary graph of video data flow within the system. The most simple case is a "star" architecture, when several Viinex 2.0 instances with replication sources functioning on them, push their video data to a Viinex 2.0 instance in a logical "center". In its turn, such central instance can act as a peer providing its video data to an instance positioned higher in some hierarchy, which makes possible to gather media data in a distributed system of a large scale.
Configuration: divide and conquer
Viinex 2.0 configuration document format is designed to be simple and manageable. There are no implicit interconnections between Viinex remote components, which ensures that a configured system always can be ran autonomously. All the links between Viinex components and references within one configuration are treated as local. That's why a namespace clash can never occur for components running in a single Viinex 2.0 instance. At the same time, several predefined configurations can be easily combined to deploy them in a single Viinex instance, by simply merging that configurations into one configuration document or into one configuration directory. This makes it possible to run several predefined aggregates of Viinex components, preseving the links within such aggregates, - in a single Viinex instance, or on multiple Viinex instances, when required by application which uses Viinex 2.0.