Gateways having localized in memory databases and business logic execution

Abstract

A gateway is provided that includes an integration gateway portion, a domain gateway portion, and a hyper-memory portion is provided. The integration gateway portion has an integration rules engine, a search engine, and a first virtual machine. The domain gateway portion has a domain rules engine. The hyper-memory portion has a hyper-memory engine, a hyper-memory, and a second virtual machine. The integration portion accesses a database via the integration rules engine and the first virtual machine or via the search engine and the first virtual machine. The domain gateway portion accesses datasets of the database that are resident in the hyper-memory via the domain objects rules engine and the hyper-memory engine or via the search engine, the second virtual machine, and the hyper-memory engine.

1 . A data communication system, comprising:
 a first software application;   a second software application having a database having datasets therein; and   a gateway device in communication with the first software application via a first communication channel and in communication with second software application via a second communication channel, the gateway device comprising
 an integration portion having an rules engine, a search engine, and a first virtual machine; 
 a domain portion having a domain rules engine; and 
 a hyper-memory portion having a hyper-memory engine, a hyper-memory, and a second virtual machine, the hyper-memory having datasets of the database resident thereon, 
   wherein the hyper-memory portion is configured to provide the first software application a resolution or query time for the datasets of less than 1 millisecond by accessing: the datasets in the database via the integration rules engine; the datasets in the database via the search engine and the first virtual machine; the datasets in the hyper-memory portion via the search engine, the second virtual machine, and the hyper-memory engine; and the datasets in the hyper-memory portion via the domain rules engine and the hyper-memory engine.   
     
     
         2 . The system according to  claim 1 , wherein the hyper-memory portion further comprises a mass loader interface and an event reader. 
     
     
         3 . The system according to  claim 2 , wherein the mass loader interface reads the datasets from the database and, via the hyper-memory engine, stores the datasets in the hyper-memory. 
     
     
         4 . The system according to  claim 1 , wherein the hyper-memory portion further comprises an event reader that parses events that are stored in the database. 
     
     
         5 . The system according to  claim 1 , wherein the first and second communication channels are selected from the group consisting of an Internet, a Local Area Network (LAN), a Wide Area Network (WAN), a wireless network, and any combinations thereof. 
     
     
         6 . The system according to  claim 1 , wherein the search engine further comprises an Object Relational Service. 
     
     
         7 . The system according to  claim 6 , wherein the Object Relational Service the Interface Definition Service determine a configuration of the datasets loaded in the hyper-memory. 
     
     
         8 . The system according to  claim 1 , further comprising an Object Request Broker service, a communication layer, and an Interface Definition Service, the Object Request Broker service, communication layer, and Interface Definition Service providing communication from the first software application to the gateway device.