Hydra Data Manager

The Hydra Data Application Manager is a system for synchronizing multiple instances of NetXposure Core (“instances”). The applications for this technology are numerous — providing the foundation for robust and scalable enterprise DAM deployments.

High Availability, Massive Scalability and Resource Control

Typically, Hydra Data Manager is used to either provide failover capabilities, massive scalability, or resource control. In any of these applications, the setup is generally the same: multiple NetXposure instances are deployed, and traffic to the DAM is routed through a network load-balancer (NLB).

Depending on how your NLB is configured, for a high availability configuration, you might have two instances deployed — a primary and a secondary instance. The NLB routes traffic to the primary. All the while, the NLB has a heart-beat monitor on the primary; and if it detects an outage, the NLB automatically begins routing traffic to the secondary until the primary is restored.

In a scalability configuration, you can deploy any number of instances, configuring your NLB to direct traffic in a round-robin sequence which distributes the traffic load across all available instances. In this configuration, the NLB can be configured to automatically remove traffic from an instance that is either too slow or is not available otherwise. This configuration provides for massive scalability of the DAM by scaling horizontally as your traffic needs dictate.

Lastly, you can route specific user populations to specific instances in order to control and manage your underlying server resources more efficiently. For example, you might load-balance two instances for general usage, while dedicating a third instance exclusively to administrative importers who are responsible for timely ingestion of new assets into the cluster.


Network Load Balancer

The Hydra Data Manager can work in conjunction with a wide range of load-balancing technologies and vendors, such as Barracuda, F5, Microsoft, and Squid. The only requirement is that the NLB provide for “sticky” sessions; each user must be routed to a specific instance. The actual “failover” responsibility rests with the NLB. Either configuration option — for failover or for scalability — will require a configuration (and functionality) for “heart-beat” monitoring and automatic failover routing to the secondary server(s).


The Hydra Data Manager manages the instances and synchronizes the data between them. All instances share a central database and a central repository for asset file storage. Hydra Data Manager manages concurrency, collisions, and caching management between the instances.

The underlying messaging system is robust and threaded. Message times can be configured; but generally updates are pushed across all instances within minutes to ensure that your data is quickly and reliably available to all users.