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: 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: 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.