Coffing Data Warehousing Software

Managing Data vs. Traffic

Data Movement: Building Network Highways and Roads to Empower Your Organization

President Dwight D. Eisenhower’s vision for American mobility was a driving force behind the creation of the modern U.S. Interstate Highway System in the 1950s.

Among Eisenhower’s many contributions, none has more profoundly changed the shape of American life than the legacy of the modern system of highways. Creating a proper infrastructure is essential for managing traffic — and the same goes for computer networking.

To travel in the U.S. by car, truck, or motorcycle, one can travel highways for long distances, but they also have the option of using roads to travel almost everywhere else. Predicting traffic patterns is key when building highways and roads. The end goal is to keep traffic flowing consistently through the peaks and valleys of the day’s rush hours.

Is there anything more frustrating than sitting in stopped traffic? There is. How about sitting in stopped traffic waiting for your PC to respond!

Network Traffic Is Like a Highway

Companies managing data must also predict network traffic as they manage their many different systems. Many companies still use mainframes: SQL Server, Oracle, DB2, Netezza, Teradata, Greenplum, Redshift, Vertica and their Hadoop systems. Accessing many different systems is extremely difficult, so the enterprise takes predicting network traffic seriously.

Having a traffic jam in your network is such a disaster that most companies won’t allow users to move data across different platforms. This means that nobody can do Federated queries, often referred to as cross-system joins.

But we have completely solved this problem!

Goodbye Network Saturation

Before we released the NexusCore Server, a user moving data could saturate the local network. Why? The data moved from the source system to the user’s PC and then to the target system. That would kill the network along with other variables that could potentially bring everything to a halt.

The network becomes saturated if a ton of users try to move data simultaneously or if a single user moves data that is too large. You don’t move a truck convoy through downtown New York city traffic.

That is why we invented the NexusCore Server. The NexusCore Server acts as a highway for any user wanting to move data. The NexusCore Server impersonates the user’s credentials and moves the data for the user as the user (as if the user was sitting at the server). This makes moving data like driving on the highway.

Now, companies can get the best of both worlds. The Nexus Query Chameleon can not only query every system within the enterprise, but it has a Super Join Builder that writes the SQL for the user. Nexus automatically builds Federated queries for the user easily — and the brilliant part is that network traffic is controlled and managed.

The combination of the Nexus Query Chameleon and the NexusCore Server allows the user to move data between systems in real time, and now anyone can perform cross-system joins without any network saturation.

Think of the Nexus on the desktop as your “roads,” and the NexusCore Server as your “highway.” You need both for a proper infrastructure.

Ready to bring your organization into the twenty-first century? Contact us here for a demo of the Nexus software.