Dependency manager for databases

Abstract

The present disclosure relates to in-memory databases or search engines using a dependency manager or configuration manager for maintaining configuration in the database system. The system may include a supervisor that may request and receive data from dependency manager, where the supervisor may be linked to other components in the system. The dependency manager may be used as a container for data metadata, and software components, which may be used in the system configuration. The configuration may be developed through a dependency system, where the dependency manager may keep an entire dependency tree for all software and data in the system. Similarly, dependency manager may create a deployable package to guarantee deployment integrity and to ensure a successful execution of any suitable software and data in the system.

What is claimed is: 
     
         1 . A method comprising:
 sending, by a first node, a first instruction to a second node, wherein the first instruction instructs the second node to retrieve a package file locally and then to send the package file to the first node upon retrieval, wherein the package file is associated with a third node based on a dependency tree before the second node receives the first instruction, wherein the package file contains a set of dependency files based on the dependency tree, wherein the first node, the second node, and the third node define a cluster hosting an in-memory database;   in response to receiving the package file from the second node based on the first instruction, sending, by the first node, the package file and a second instruction to the third node, wherein the second instruction instructs the third node to install the set of dependency files from the package file locally.   
     
     
         2 . The method of  claim 1 , wherein the first node sends the first instruction to the second node in response to the first node detecting a dependency failure on the third node based on the first node interpreting a heartbeat signal received from the third node. 
     
     
         3 . The method of  claim 2 , further comprising:
 determining, by the first node, if the third node installed the set of dependency files from the package file successfully.   
     
     
         4 . The method of  claim 1 , wherein the dependency tree is based on at least one of a partition, a module, a file, or a record, wherein the in-memory database comprises at least one of the partition, the module, the file, or the record. 
     
     
         5 . The method of  claim 1 , wherein the second node fetches a dependency from a data frame and then compiles the package file. 
     
     
         6 . The method of  claim 1 , wherein each of the dependency files is determined by the second node via the dependency tree associated with the third node. 
     
     
         7 . The method of  claim 6 , wherein each of the dependency files is based on a comparative relationship of that dependency file with a corresponding dependency file installed on a subset of nodes in the cluster. 
     
     
         8 . The method of  claim 1 , further comprising:
 receiving, by the first node, a third instruction from a server external to the cluster, wherein the server is associated with at least one of the dependency files installed on the third node based on the second instruction, wherein the third instruction instructs the third node to perform an update to the package file on the third node such that the at least one of the dependency files is updated via the server.   
     
     
         9 . A system comprising:
 a first node;   a second node; and   a third node, wherein the first node, the second node, and the third node define a cluster hosting an in-memory database, wherein the first node is programmed to:
 send a first instruction to the second node, wherein the first instruction instructs the second node to retrieve a package file locally and then to send the package file to the first node upon retrieval, wherein the package file is associated with the third node based on a dependency tree before the second node receives the first instruction, wherein the package file contains a set of dependency files based on the dependency tree; 
 send the package file and a second instruction to the third node in response to receiving the package file from the second node based on the first instruction, wherein the second instruction instructs the third node to install the set of dependency files from the package file locally. 
   
     
     
         10 . The system of  claim 9 , wherein the first node is programmed to send the first instruction to the second node in response to the first node detecting a dependency failure on the third node based on the first node interpreting a heartbeat signal received from the third node. 
     
     
         11 . The system of  claim 10 , wherein the first node is programmed to:
 determine if the third node locally installed the set of dependency files from the package file successfully.   
     
     
         12 . The system of  claim 9 , wherein the dependency tree is based on at least one of a partition, a module, a file, or a record, wherein the in-memory database comprises at least one of the partition, the module, the file, or the record. 
     
     
         13 . The system of  claim 9 , wherein the second node fetches a dependency from a data frame and then compiles the package file. 
     
     
         14 . The system of  claim 9 , wherein each of the dependency files is determined by the second node via the dependency tree associated with the third node. 
     
     
         15 . The system of  claim 14 , wherein each of the dependency files is based on a comparative relationship of that dependency file with a corresponding dependency file installed on a subset of nodes in the cluster. 
     
     
         16 . The system of  claim 15 , wherein the first node is programmed to:
 receive a third instruction from a server external to the cluster, wherein the server is associated with at least one of the dependency files installed on the third node based on the second instruction, wherein the third instruction instructs the third node to perform an update to the package file on the third node such that the at least one of the dependency files is updated via the server.