Abstract: Software is increasingly being developed as a collection of loosely coupled applications. Loosely coupled applications exchange data by publishing data to and retrieving data from a data store, such as a database, a file located on a storage cluster, etc. Data produced by one application and consumed by another is referred to as a data dependency. In some embodiments, an application's data dependencies are identified by analyzing cached query plans associated with the application. Query plans include a hierarchical representation of a query, where non-leaf nodes represent commands and leaf nodes identify data dependencies. An application's data dependencies are identified by traversing the hierarchical representation of the query. Data dependencies consumed by the application are identified by finding leaf nodes that descend from a read command, while data dependencies produced by the application are identified by finding leaf nodes that descend from a write command.

Abstract: Software is increasingly being developed as a collection of loosely coupled applications. Loosely coupled applications exchange data by publishing data to and retrieving data from a data store, such as a database, a file located on a storage cluster, etc. Data produced by one application and consumed by another is referred to as a data dependency. In some embodiments, an application's data dependencies are identified by analyzing cached query plans associated with the application. Query plans include a hierarchical representation of a query, where non-leaf nodes represent commands and leaf nodes identify data dependencies. An application's data dependencies are identified by traversing the hierarchical representation of the query. Data dependencies consumed by the application are identified by finding leaf nodes that descend from a read command, while data dependencies produced by the application are identified by finding leaf nodes that descend from a write command.

Abstract: Methods, systems, and computer storage media are provided for providing an application programming interface (“API”) for executing a query are provided. The API call, scheduling, and assignment processing engines may generate and schedule assignments, along with associated dataset portions, based on the query. Based on the assignments and datasets, the assignments may be scheduled for execution by processes of nodes in a distributed system. The API call and query may also include implementation instructions that require storing dataset portions into memory that is associated with a process executing the assignment for an in-memory database implementation. As the assignment is executed using a dataset portion that is stored on memory associated with a process, results may be stored in a file. Once each assignment has been executed and has a result file, the result files are merged to provide results of the query and API call to the user.

Abstract: Software is increasingly being developed as a collection of loosely coupled applications. Loosely coupled applications exchange data by publishing data to and retrieving data from a data store, such as a database, a file located on a storage cluster, etc. Data produced by one application and consumed by another is referred to as a data dependency. In some embodiments, an application's data dependencies are identified by analyzing cached query plans associated with the application. Query plans include a hierarchical representation of a query, where non-leaf nodes represent commands and leaf nodes identify data dependencies. An application's data dependencies are identified by traversing the hierarchical representation of the query. Data dependencies consumed by the application are identified by finding leaf nodes that descend from a read command, while data dependencies produced by the application are identified by finding leaf nodes that descend from a write command.

Abstract: Methods, systems, and computer storage media are provided for providing an application programming interface (“API”) for executing a query are provided. The API call, scheduling, and assignment processing engines may generate and schedule assignments, along with associated dataset portions, based on the query. Based on the assignments and datasets, the assignments may be scheduled for execution by processes of nodes in a distributed system. The API call and query may also include implementation instructions that require storing dataset portions into memory that is associated with a process executing the assignment for an in-memory database implementation. As the assignment is executed using a dataset portion that is stored on memory associated with a process, results may be stored in a file. Once each assignment has been executed and has a result file, the result files are merged to provide results of the query and API call to the user.

Abstract: Software is increasingly being developed as a collection of loosely coupled applications. Loosely coupled applications exchange data by publishing data to and retrieving data from a data store, such as a database, a file located on a storage cluster, etc. Data produced by one application and consumed by another is referred to as a data dependency. In some embodiments, an application's data dependencies are identified by analyzing cached query plans associated with the application. Query plans include a hierarchical representation of a query, where non-leaf nodes represent commands and leaf nodes identify data dependencies. An application's data dependencies are identified by traversing the hierarchical representation of the query. Data dependencies consumed by the application are identified by finding leaf nodes that descend from a read command, while data dependencies produced by the application are identified by finding leaf nodes that descend from a write command.

Abstract: Software is increasingly being developed as a collection of loosely coupled applications. Loosely coupled applications exchange data by publishing data to and retrieving data from a data store, such as a database, a file located on a storage cluster, etc. Data produced by one application and consumed by another is referred to as a data dependency. In some embodiments, an application's data dependencies are identified by analyzing cached query plans associated with the application. Query plans include a hierarchical representation of a query, where non-leaf nodes represent commands and leaf nodes identify data dependencies. An application's data dependencies are identified by traversing the hierarchical representation of the query. Data dependencies consumed by the application are identified by finding leaf nodes that descend from a read command, while data dependencies produced by the application are identified by finding leaf nodes that descend from a write command.