Cognitive Database Management for Data Lake Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional data lake systems rely on manual selection of operational databases, which is inefficient and impractical for managing large volumes of data, as schema application is delayed until data is queried, lacking automated cognitive methods for data classification and database recommendation.

Innovation Solution

Implementing a cognitive, self-learning method that categorizes streaming files based on metadata and recommends suitable operational databases by building a knowledge base using historical data, employing machine learning and analytics to identify optimal database engines for data transformation and processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual selection of operational databases is used, then flexibility in database choice is maintained, but efficiency and scalability deteriorate when managing large volumes of data

Engineering Contradiction:
Improvedata management efficiencyVSAvoidautomated database selection
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The system performs self-service by automatically analyzing incoming data characteristics and selecting appropriate operational databases without human intervention. The data lake system itself evaluates data types, formats, and access patterns, then autonomously provisions the most suitable database engine, eliminating the need for manual database selection while maintaining optimal performance

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system dynamically changes operational parameters by adjusting database selection based on real-time data characteristics. It monitors data type, structure, access patterns, and volume metrics, then transforms these observations into automated database provisioning decisions, adapting the system behavior to match current data requirements rather than relying on static manual configuration

Inventive Principle:
Principle #35Parameter changes

2Productivity

If schema application is delayed until data is queried, then data flexibility is maintained, but data access efficiency deteriorates

Engineering Contradiction:
Improvedata access efficiencyVSAvoidschema management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by applying schemas to data at the time of ingestion rather than waiting for query time. When data enters the data lake, the system automatically analyzes its structure, infers the appropriate schema, and applies it immediately, enabling faster data access later without requiring complex real-time schema generation during queries

Inventive Principle:
Principle #10Preliminary action

3Productivity

If automated cognitive methods are implemented, then data classification efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvedata classification speedVSAvoidcognitive system architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system replaces mechanical manual classification methods with cognitive automation. Instead of relying on manual data tagging or simple rule-based systems, it employs machine learning models and analytics engines that automatically classify data based on its characteristics, patterns, and usage requirements, significantly improving classification speed and accuracy

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11119980B2Self-learning operational database management
Publication Date: 2021.09.14 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11119980B2 patent drawing
  • US11119980B2 patent drawing
  • US11119980B2 patent drawing

AI summary

Systems, methods, tools and computer programming products for implementing a cognitive data lake that selects or recommends operational database based on historically created data lakes storing files having similar file types, categorizations, metadata, and/or frequency of file usage. Selecting the appropriate operational databases is streamlined by building a knowledge base that is accessible during the creation and/or registration of each data lake. The knowledge base maintains historical records of past data lakes, describing each historical data lake's file types, attributes, metadata, frequency of file usage and at least one operational database implemented to manage the files of the historical data lake. Incoming files streamed or stored by the data lake are analyzed for metadata (extracted from the files as well as separate metadata), categorized based on the metadata, and matched to one or more operational databases of the historical data lakes described by knowledge base, known to manage similar files.