Three-Tier Database Management Tool for Cell-Wise Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern enterprises face difficulties in managing vast volumes of data due to the lack of effective controls for confidentiality and data integrity, and existing database systems struggle with efficient access and updating of data, leading to issues like locking problems and interference between user requests.
Innovation Solution
A three-tier database management tool is introduced, comprising a first-tier database for historical data, a second-tier database for current data, and a third-tier database for complete records, along with a cache system that rebuilds based on the third-tier database's state, enabling fast searching and cell-wise access policy management through a client application that enforces access permissions and propagates edits across databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored in mass storage devices with traditional database management, then data confidentiality and integrity can be maintained, but data access and updating become slow and interfere with concurrent user requests
Solution Approach 1:
The database is segmented into three distinct tiers: first-tier for historical data, second-tier for current data, and third-tier for complete records. This segmentation allows concurrent access patterns to be optimized by directing different types of operations to appropriate tiers, improving overall access speed while maintaining data integrity through structured organization.
Solution Approach 2:
A cache system acts as an intermediary layer between users and the three-tier database structure. The cache stores frequently accessed data and manages access requests, reducing direct access overhead to the database and enabling faster data retrieval while maintaining confidentiality and integrity controls.
2Reliability
If traditional database locking mechanisms are used to ensure data integrity, then data confidentiality is maintained, but locking problems arise that interfere with concurrent user requests
Solution Approach 1:
By dividing the database into three independent tiers, the system eliminates the need for centralized locking mechanisms. Each tier can be accessed and updated independently based on its specific purpose, allowing multiple users to work concurrently on different data types without interference or locking conflicts.
Solution Approach 2:
The cache creates copies of frequently accessed data from the database tiers, allowing users to access and work with data copies simultaneously without blocking each other. This copying mechanism enables concurrent operations while maintaining data integrity through the structured three-tier architecture.
3Reliability
If fine-grained access control is implemented at the cell level, then data security is improved, but system complexity increases
Solution Approach 1:
The three-tier database structure naturally segments data by its access patterns and sensitivity levels. Historical data, current data, and complete records can have different access control policies applied to each tier, simplifying the implementation of fine-grained security without requiring complex cell-level controls throughout the entire system.
Solution Approach 2:
The cache system serves as an intermediary that manages access control at a higher level, reducing the need for complex cell-level security mechanisms. By controlling access to the cache and the three-tier structure, the system achieves fine-grained security with reduced overall complexity.
Data Source
AI summary
A method of managing data using a three-tier database to support fast searching and cell-wise access policy management. The method comprises determining access permissions to a three-tier database associated with a user interface by a client application executing on a computer system, wherein the access permissions are applied on a per data cell basis and on a per record basis; presenting records of a selected table of the three-tier database in accordance with the access permissions associated with the user interface by the client application to the user application; receiving an edit by the client application from the user interface; writing the edit to the three-tier database by the client application in accordance with the access permissions; and propagating by the client application change notifications indicating the edit to a plurality of client instances associated with different user interfaces.