Graph Database Multidimensional Model Software Dependency Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing systems face complexity in managing dependencies between software components and hardware resources, leading to difficulties in tracking and managing events and failures, due to the lack of a comprehensive view of resource allocations and dependencies.

Innovation Solution

A system that uses a graph database to store and manage multidimensional models of software offerings, representing service components, resources, and their dependencies, facilitating efficient retrieval and display of model data, impact analysis, and real-time management within a graphical user interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If cloud computing systems share infrastructure resources to improve utilization rates, then resource utilization efficiency is improved, but complexity in managing dependencies between software components and hardware resources increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoiddependency management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a multidimensional model as an intermediary layer between software components and hardware resources. This model includes service components, resources, and their dependencies, stored in a graph database. The intermediary model simplifies dependency tracking by providing a structured representation that separates the complexity of resource sharing from software management, allowing efficient querying and impact analysis without reducing resource utilization benefits.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive tracking of resource allocations and dependencies is implemented, then fault diagnosis capability is improved, but system overhead increases

Engineering Contradiction:
Improvefault diagnosis capabilityVSAvoidsystem overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the system into distinct components: service components, resources, and their dependencies, each represented as separate entities in a multidimensional model. This segmentation allows comprehensive tracking of allocations and dependencies without creating a monolithic complex system. The graph database stores these segmented elements with explicit relationships, enabling efficient fault diagnosis through targeted queries while maintaining manageable system overhead through modular organization.

Inventive Principle:
Principle #1Segmentation

3Speed

If graph database is used to store multidimensional models, then query response time is improved, but data storage complexity increases

Engineering Contradiction:
Improvequery response timeVSAvoiddata storage complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent transitions from traditional tabular data storage to a graph-based multidimensional model, adding a new dimensional structure to data organization. The graph database represents service components, resources, and dependencies as nodes and edges in a multi-dimensional space, enabling efficient traversal and querying of relationships. This dimensional change improves query response time by directly modeling relationships rather than requiring complex joins, while the graph structure itself manages the storage complexity through intuitive node-edge representation.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS10528897B2Graph databases for storing multidimensional models of software offerings
Publication Date: 2020.01.07 INTUIT INC
  • US10528897B2 patent drawing
  • US10528897B2 patent drawing
  • US10528897B2 patent drawing

AI summary

The disclosed embodiments provide a system that facilitates the maintenance and execution of a software offering. During operation, the system obtains model data associated with a multidimensional model of the software offering. Next, the system stores the model data in a graph database. Finally, the system uses the graph database to facilitate management of the software offering.