Pluggable architecture for embedding analytics in clustered in-memory databases

Abstract

Disclosed are pluggable, distributed computing-system architectures allowing for embedding analytics to be added or removed from nodes of a system hosting an in-memory database. The disclosed system includes an API that may be used to create customized, application specific analytics modules. The newly created analytics modules may be easily plugged into the in-memory database. Each user query submitted to the in-memory database may specify different analytics be applied with differing parameters. All analytics modules operate on the in-memory image of the data, inside the in-memory database platform. All the analytics modules, may be capable of performing on-the-fly analytics, which may allow a dynamic and comprehensive processing of search results.

What is claimed is: 
     
         1 . A system comprising:
 a first node including a main memory configured to store a record of an in-memory database;   a second node including a processor configured to receive a request for an action involving a software component, to input a query result into the software component, and to execute the software component based on the query result, wherein the query result is based on the record; and   a third node configured to supervise the second node and to receive a heartbeat signal from the second node, wherein the heartbeat signal is informative of the second node receiving the software component.   
     
     
         2 . The system of  claim 1 , further comprising:
 a fourth node configured to transmit the query result to the second node based on a determination if a search query contains the request for the action.   
     
     
         3 . The system of  claim 2 , wherein the fourth node is configured to identify the second nodes prior to transmitting the search query to a fifth node. 
     
     
         4 . The system of  claim 3 , wherein the fourth node is configured to determine an action parameter to be applied prior to transmitting the search query to the fifth node. 
     
     
         5 . The system of  claim 2 , wherein the fourth node is configured to determine if the search query contains the request for the action and to identify the second node executing the software component. 
     
     
         6 . The system of  claim 5 , further comprising:
 a fifth node configured to execute a search conductor query and to send a subset of the query result containing a record of a sixth node satisfying the search conductor query based on a receipt of the search conductor query from the fourth node, wherein the fourth node is configured to generate the search conductor query based on the search query, wherein the fourth node is configured to send the search conductor query to the fifth node.   
     
     
         7 . The system of  claim 6 , wherein the fourth node is configured to aggregate the subset of the query result received from the fifth node and thereby generate the query result. 
     
     
         8 . The system of  claim 6 , wherein the fourth node is configured to send a record in the query result to the second node, wherein the record in the query result is compressed. 
     
     
         9 . The system of  claim 1 , wherein the software component includes at least one of a disambiguation module, a linking module, a scoring module, or a link-in-real-time module. 
     
     
         10 . The system of  claim 1 , further comprising:
 a fourth node configured to send the software component to a data store based on receiving the software component from a remote data source, wherein the second node is configured to retrieve the software component from the data store before the query result is input.   
     
     
         11 . The system of  claim 1 , further comprising:
 a fourth configured to validate the search query based on a programming interface.   
     
     
         12 . The system of  claim 1 , further comprising:
 a fourth node configured to store the software component in an agent and to generate the software component based on a programming interface.   
     
     
         13 . The system of  claim 2 , wherein the fourth node is configured to receive the search query from a remote data source. 
     
     
         14 . The system of  claim 1 , wherein the component includes a module. 
     
     
         15 . The system of  claim 1 , wherein the third node is configured to request that the software component be sent from a data store to the second node according to a dependency tree stored in a fourth node and before the query result is input, wherein the third node is configured to supervise the fourth node. 
     
     
         16 . The system of  claim 1 , wherein the action includes an analytic. 
     
     
         17 . The system of  claim 1 , wherein the second node is configured to host an agent configured to run the software component. 
     
     
         18 . The system of  claim 1 , wherein the software component is configured for selectively plugging into the second node and selectively unplugging from the second node.