Writable Partitions in Read-Only Replicated Records to Reduce Joins
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database replication methods restrict clients from directly augmenting or appending data to replicated database portions, leading to inefficiencies and complex management due to the read-only nature of replicated tables, which necessitate additional structures and resource-intensive join operations.
Innovation Solution
Implementing writable partitions within read-only replicated database tables, allowing clients to directly append or integrate additional data by creating one or more columns in a writeable partition alongside read-only partitions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If replicated database tables are designated as read-only, then data integrity and replication consistency are improved, but client ability to directly augment or append data deteriorates
Solution Approach 1:
The database table is segmented into two distinct partitions: a read-only partition containing replicated data and a writeable partition containing client-specific data. This segmentation allows simultaneous maintenance of data integrity through replication while enabling client data augmentation through the writeable partition, resolving the contradiction between reliability and adaptability.
Solution Approach 2:
Different partitions of the same database table are assigned different access permissions and functional qualities. The read-only partition maintains strict data integrity for replicated data, while the writeable partition provides adaptability for client-specific data. This local differentiation of quality attributes resolves the contradiction by applying appropriate characteristics to specific portions of the system.
2Quantity of substance
If new database structures are created to store additional client data, then data storage capability is improved, but storage overhead and device complexity increase
Solution Approach 1:
The patent merges the replicated data and client-specific data into a single unified database table with distinct partitions. This eliminates the need for separate database structures, foreign keys, and join operations that would otherwise be required. The merging approach increases data storage capability while reducing device complexity by consolidating what would otherwise be multiple separate structures.
Solution Approach 2:
The database table structure is designed to serve multiple functions simultaneously: it stores replicated read-only data, stores client-specific writeable data, and enables querying across both types of data without requiring separate structures. This multi-functionality eliminates the need for additional database structures, reducing both storage overhead and device complexity while maintaining expanded storage capability.
3Stability of the object's composition
If separate structures are used for replicated and derived data, then data organization is improved, but query performance deteriorates due to compute-intensive join operations
Solution Approach 1:
By merging replicated and derived data into a single database table with distinct partitions, the patent eliminates the need for join operations between separate structures. Queries can directly access both types of data within the same table, dramatically improving query performance while maintaining clear organizational structure through partitioning. This resolves the contradiction by removing the computational overhead of joins.
4Adaptability or versatility
If additional data structures are created to manage replicated data, then data functionality is improved, but computational resources and time requirements increase
Solution Approach 1:
The patent combines multiple data management functions into a single unified table structure, eliminating the need for computationally expensive join operations and complex data retrieval processes. This merging approach maintains enhanced data functionality while significantly reducing computational resource requirements and energy consumption for data access and manipulation.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
Techniques for using writeable partitions with read-only replicated records include one or more non-transitory computer-readable media storing program instructions that, when executed by one or more processors of an authorization server, cause the one or more processors to perform a method including receiving a replica of a portion of a database, storing the replica of the portion of the database in a read-only partition, adding a field to the portion of the database in a writeable partition, and writing data to the added field.