Flexible Index Nodes in Graph Databases

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Graph databases face limitations in index management, as traditional indexes are maintained and operated using different mechanisms than the database contents, leading to inflexibility and resource inefficiency, with limited ability to control what is indexed and where, resulting in high overhead and storage usage.

Innovation Solution

The introduction of flexible index nodes in graph databases, managed using the same rules and operators as regular nodes, allowing for creation, modification, and deletion according to application logic, enabling efficient resource utilization and configurable indexing scenarios.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional indexing systems are used in graph databases, then index management is separated from database content management, but this leads to device complexity and resource overhead

Engineering Contradiction:
Improveindex management separationVSAvoidindexing system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges index management with database content management by treating indexes as first-class graph objects. Indexes are represented as nodes within the graph database itself, allowing the same query operators and management mechanisms to handle both data and indexes uniformly, thereby reducing system complexity while maintaining reliable index management

Inventive Principle:
Principle #5Merging (Combining)

2Ease of manufacture

If traditional indexes manage all entries uniformly, then indexing is simple to implement, but this results in loss of information and resource inefficiency

Engineering Contradiction:
Improveindex implementation simplicityVSAvoidresource usage
Core Design Contradiction:
Ease of manufactureVSLoss of substance

Solution Approach 1:

The patent applies local quality by allowing different portions of the graph database to have different indexing characteristics. Individual nodes can be selectively indexed based on their importance, access patterns, and data characteristics. This enables fine-grained control over what is indexed, reducing resource consumption while maintaining implementation flexibility through graph query operations

Inventive Principle:
Principle #3Local quality

3Reliability

If indexes are maintained using different mechanisms than database contents, then index operations are specialized, but this increases device complexity and reduces adaptability

Engineering Contradiction:
Improveindex operation specializationVSAvoidindex management flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements universality by designing a system where the same graph query operators and management mechanisms serve both data retrieval and index operations. Index nodes are treated as regular graph nodes, allowing unified management through cypher queries and other graph database operations, thereby achieving both specialization through graph-optimized operations and versatility through uniform management interfaces

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11080332B1Flexible indexing for graph databases
Publication Date: 2021.08.03 AMAZON TECH INC
  • US11080332B1 patent drawing
  • US11080332B1 patent drawing
  • US11080332B1 patent drawing

AI summary

A processing device generates an index node for an attribute in a graph database, wherein the index node is linked to a second node by a first edge having a first edge type. The processing device determines a first plurality of additional nodes that have the attribute. For each node of the first plurality of additional nodes, the processing device generates an edge linking the node to the index node, wherein the edge comprises a second edge type.