Patent ID: 7483901

Claim:
In a computer network comprising two or more arbitrarily defined data structures, each of the data structures comprising one or more leaf data elements, a description of each data structure being known, a system for transferring data from a first in-memory data component corresponding to a first data structure to a second in-memory data component corresponding to a second data structure, the system comprising: a) a mapping tool configured to: allow a user to graphically define a relation and association between leaf data elements of a first data structure description and leaf data elements of a second data structure description; and generate one or more mapping descriptions of the relation and association between the leaf data elements of the first data structure description and the leaf data elements of the second data structure description as defined by the user; and b) a high-performance run-time engine configured to: dynamically generate a first in-memory data component containing actual data associated with the leaf data elements of the first data structure description, the high-performance run-time engine using a key-based look-up molding technique to generate a unique key to dynamically store and locate the actual data for each of the leaf data elements, the first in-memory data component comprising at least one lookup table configured to store each unique key for the first in-memory data component; traverse the one or more mapping descriptions and accessing the at least one lookup table of the first in-memory data component to get actual data stored in the first in-memory data component using a key-based look-up technique; dynamically generate a second in-memory data component configured to store actual data associated with the leaf data elements of the second data structure description, the high-performance run-time engine using the key-based look-up molding technique to generate a unique key to dynamically store and locate the actual data for each of the leaf data elements, the second in-memory data component comprising at least one lookup table configured to store each unique key for the second in-memory data component; and transfer data between the first in-memory data component and the second in-memory data component according to the one or more mapping descriptions.