Autonomous Database Refactoring for Mixed Data

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Relational Database Management Systems (RDBMS) face challenges in efficiently handling increasing amounts of unstructured data, as they are primarily designed for structured data, leading to inefficiencies when storing and managing unstructured data without dedicated non-relational databases.

Innovation Solution

An autonomous refactoring system (ARS) is introduced to segregate data into separate relational and non-relational databases, allowing structured data to remain in the RDBMS while unstructured data is migrated to a non-relational database, maintaining the existing user interface and API, and performing refactoring in the background to avoid service disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If unstructured data is stored in an RDBMS, then the database can handle both structured and unstructured data in a single system, but the efficiency of storing and managing unstructured data deteriorates

Engineering Contradiction:

Improveability to store both structured and unstructured dataVSAvoidefficiency of storing and managing unstructured data

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent applies segmentation by dividing the database system into two separate components: an RDBMS for structured data and a non-relational database for unstructured data. This segmentation allows each database type to operate optimally for its intended data structure, resolving the efficiency problem while maintaining the ability to handle both data types through a unified interface.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (the autonomous refactoring system with unified API) that sits between the user and the dual database system. This intermediary transparently routes structured data operations to the RDBMS and unstructured data operations to the non-relational database, maintaining adaptability while optimizing performance for each data type.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If data is segregated into separate relational and non-relational databases, then efficiency of managing unstructured data improves, but device complexity increases

Engineering Contradiction:

Improveefficiency of managing unstructured dataVSAvoidcomplexity of database system architecture

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent applies universality by creating a unified API interface that can handle both structured and unstructured data operations. This single interface performs multiple functions (routing to appropriate databases, managing different data formats, handling queries) thereby masking the underlying architectural complexity while maintaining high efficiency for unstructured data management.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The autonomous refactoring system applies self-service by automatically determining data types and routing operations to the appropriate database without requiring user intervention or complex configuration. This automation reduces the perceived complexity for users while maintaining the efficiency benefits of the segregated architecture.

Inventive Principle:

Principle #25Self-service

3Productivity

If refactoring is performed to separate unstructured data, then storage growth becomes predictable and management efficiency improves, but service disruption may occur

Engineering Contradiction:

Improvepredictability of storage growthVSAvoidcontinuity of database service

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by implementing the refactoring process in a controlled, staged manner. The system preliminarily establishes the dual database architecture and unified interface before fully separating data, allowing storage growth to become predictable while maintaining service continuity through gradual migration and fallback capabilities.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent ensures continuity of useful action by designing the refactoring process to maintain database operations throughout the transition. The unified API and dual database system allow read and write operations to continue seamlessly during the refactoring process, preventing service disruption while achieving predictable storage growth and improved management efficiency.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS11989169B2Autonomous refactoring system for database

Publication Date: 2024.05.21 SALESFORCE INC

AI summary

Techniques for refactoring data in a database are disclosed. A database may initially store both relational and non-relational data. A request to access data from a first data element in the database may be received via a relational database API. Upon receiving the request, a determination is made as to whether the first data element has been refactored into relational and non-relational portions. If the first data element has not been refactored, a refactoring operation is carried out by storing relational portions of the first data element into a relational database and the non-relational portions of the first data element into a non-relational database. The refactoring is performed concurrent with providing data to a requesting computing system. Additionally, refactoring information is updated to indicate that the first data element has been refactored.