Relational Database NoSQL Translation Module

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The integration of relational and non-relational databases poses challenges due to increased costs and technology and data security issues during synchronous maintenance, as well as limitations in performance and scalability when handling big data storage and analysis.

Innovation Solution

A relational database is enhanced to support both relational SQL access and non-relational NoSQL access by using a translation module to translate NoSQL access requests into SQL-compatible requests, allowing it to store non-relational data in a relational data table, effectively converting into a multi-model database supporting both relationship and wide column store models.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If both a relational database and a non-relational database are deployed for the same client or application, then data security and high availability are improved, but costs increase and technology maintenance complexity increases

Engineering Contradiction:

Improvedata security and high availabilityVSAvoidtechnology maintenance complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges relational database (SQL) and non-relational database (NoSQL) functionalities into a single database system. The database can store data in both relational table models and non-relational document models, and can process both SQL queries and NoSQL queries through a unified query processing module, eliminating the need for separate database deployments

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The database system achieves multi-functionality by supporting multiple data models (relational and non-relational) and multiple query languages (SQL and NoSQL) within a single system. The query processing module can automatically identify and process different query types, making the database universal enough to handle both traditional relational workloads and modern non-relational requirements

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If both a relational database and a non-relational database are deployed for the same client or application, then data security and high availability are improved, but costs increase

Engineering Contradiction:

Improvedata security and high availabilityVSAvoidcosts

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent combines the functionality of separate relational and non-relational database deployments into a single database instance. This consolidation reduces infrastructure costs, licensing fees, and operational expenses associated with maintaining multiple database systems while preserving the security and availability benefits

Inventive Principle:

Principle #5Merging (Combining)

3Reliability

If a conventional relational database is used, then data security and high availability are provided, but performance and scalability are limited when dealing with big data

Engineering Contradiction:

Improvedata security and high availabilityVSAvoidperformance and scalability

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The database implements dynamic adaptability by allowing the data model structure to change flexibly. Non-relational data models enable dynamic schema changes and flexible data organization that can scale with big data requirements, while the system maintains relational integrity and security features when needed

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system changes the data organization parameters by supporting both fixed relational schemas and flexible non-relational document models. This parameter flexibility allows the database to optimize for performance and scalability when handling large volumes of diverse data while maintaining security and availability guarantees

Inventive Principle:

Principle #35Parameter changes

4Adaptability or versatility

If a non-relational database is used, then storage flexibility and rapid development are improved, but data security and high availability are compromised

Engineering Contradiction:

Improvestorage flexibilityVSAvoiddata security and high availability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent merges the storage flexibility of non-relational databases with the security and availability guarantees of relational databases. The system can store flexible non-relational data while enforcing relational integrity constraints, transaction management, and security protocols through its unified architecture

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS11797533B2Data storage apparatus, translation apparatus, and database access method

Publication Date: 2023.10.24 BEIJING OCEANBASE TECHNOLOGY CO LTD

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for accessing a relational database using requests that conform to a non-structure query language syntax. In one aspect, a method includes receiving, from a client, a first access request that conforms to a NoSQL syntax for accessing a wide column store, wherein the first access request comprises a first event feature and a first attribute feature that are related to the wide column store, and the first attribute feature comprises a column family feature of the wide column store; translating the first access request into a second access request that conforms to a SQL syntax, wherein the second access request comprises a second event feature corresponding to the first event feature and a second attribute feature corresponding to the first attribute feature; and forwarding the second access request to a relational database.