Hybrid Database Query Visualization for Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database systems face challenges such as complexity in designing and maintaining relational databases, inefficiencies in object databases, and scalability issues in graph databases, particularly with large datasets and frequent data updates, which lead to performance penalties and difficulties in real-time extension and user-friendly query processes.
Innovation Solution
A connection-oriented database system that stores data in a non-hierarchical manner, allowing users to explore data through abstract classes and data objects without needing SQL knowledge, with a user interface that generates incremental queries and visualizes relationships using graphical elements, enabling fast data exploration and query processing without performance penalties.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If relational databases are used to store data in tables with defined relationships, then data access and verification are improved, but system complexity increases and scaling becomes difficult
Solution Approach 1:
The patent segments the monolithic relational database structure into multiple specialized database systems (relational, object, graph databases) that can operate independently and be scaled separately. Each database type handles specific data access patterns, reducing overall system complexity while maintaining reliable data access through appropriate technology selection for each segment.
Solution Approach 2:
The patent introduces a new dimension to data storage by implementing a hybrid architecture that combines traditional relational tables with object-oriented structures and graph relationships. This multi-dimensional approach allows data to be accessed through multiple pathways (relational queries, object references, graph traversals), improving access reliability without increasing the complexity of any single access path.
2Ease of operation
If object databases are used to store complex data and relationships directly, then ease of operation is improved, but access speed decreases due to late binding
Solution Approach 1:
The patent applies local quality by implementing early binding for specific object types that require fast access while maintaining late binding flexibility for other objects. The system dynamically selects the appropriate binding strategy based on the local requirements of each data access operation, achieving both ease of operation and high speed where needed.
Solution Approach 2:
The patent introduces dynamics by making the binding strategy adaptive rather than static. The hybrid object-relational system can switch between early and late binding modes depending on the operational context, data type, and performance requirements, allowing the system to optimize for both ease of operation and access speed in different scenarios.
3Adaptability or versatility
If graph databases are used to represent web-based data structures, then adaptability is improved, but memory requirements increase
Solution Approach 1:
The patent applies partial action by implementing graph database structures only for the specific portions of data that require web-based hierarchical representation, while other data remains in more compact relational or object formats. This selective approach maintains the adaptability needed for web data structures while minimizing overall memory consumption by avoiding universal graph representation.
4Adaptability or versatility
If database structures are modified in production systems, then adaptability is improved, but service interruptions occur due to locking
Solution Approach 1:
The patent applies preliminary action by pre-defining flexible schema structures and data models that can accommodate future requirements without requiring structural modifications. The hybrid architecture is designed with extensibility built-in from the beginning, allowing new data types and relationships to be added through configuration rather than structural changes, thus avoiding production interruptions.
Solution Approach 2:
The patent introduces an intermediary layer (the hybrid object-relational interface) that mediates between the physical database structure and the logical data access patterns. This intermediary allows schema evolution and structural modifications to occur in the physical layer without affecting service continuity at the logical layer, as the intermediary absorbs and manages the transitions.
Data Source
AI summary
A method for providing visualization of data objects in a relational database is provided. The method comprises: (a) bringing an electronic device of a user in communication with a server comprising the non-hierarchical relational database, (b) generating and displaying a graph comprising visual graphical elements including a first node representing a first class encompassing a first subset of the data objects, a second node representing a second class encompassing a second subset of the data objects, and a link representing a relationship between the first class and the second class, (c) receiving a request via the user interface of the electronic device to perform a task directed to at least a subset of the data objects, (d) generating one or more filtering operations for the task and, upon execution, producing a graphical result comprising a filtered data set, and (e) automatically displaying the graphical result on the user interface.