Issue Management System Partial Database Caching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing governance, risk, and compliance (GRC) software systems are complex to install and use, leading to performance issues when retrieving issue records, particularly in large organizations, due to raw data formats and large databases, which frustrate users and limit system utility.
Innovation Solution
A method and system that improves response time by creating a partial database on a remote device based on filtering parameters, allowing local query performance without server calls, and pre-evaluating database entries to reduce function evaluation needs, enabling efficient search techniques and displaying relevant metrics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If a full database is maintained on the server for large organizations, then data completeness is improved, but query response time deteriorates due to large database size
Solution Approach 1:
The patent segments the full database into multiple sharded databases distributed across different servers. Each sharded database contains a subset of the total data, allowing queries to be processed in parallel across multiple nodes rather than scanning a single large database, thus improving query response time while maintaining data completeness through distributed storage
Solution Approach 2:
The patent implements caching mechanisms that store frequently accessed data subsets locally on client devices or intermediate servers. This partial action approach keeps only the most commonly queried data readily available locally, eliminating the need to retrieve entire datasets from the server for routine queries, thereby reducing response time while maintaining access to complete data when needed
2Device complexity
If raw data formats are used to mimic database storage structure, then data storage simplicity is improved, but user operation complexity increases due to unprocessed data presentation
Solution Approach 1:
The patent applies preliminary action by pre-processing and transforming raw database data into standardized, user-friendly formats before presentation. Data is aggregated, filtered, and formatted in advance according to common user needs, so when users query the system, they receive pre-processed information rather than raw data requiring manual interpretation, thus reducing operational complexity while maintaining storage simplicity
Solution Approach 2:
The patent introduces an intermediary data transformation layer between the database storage system and the user interface. This intermediary component acts as a mediator that translates raw database formats into standardized presentation formats, handling data aggregation, filtering, and formatting automatically, thereby decoupling storage simplicity from presentation complexity
3Adaptability or versatility
If database functions reference values stored in other entries, then data relationships are improved, but query performance deteriorates due to function evaluation overhead
Solution Approach 1:
The patent applies preliminary action by pre-evaluating database functions and computing derived values during data insertion or periodic updates. When a function references values from other entries, the system proactively computes the result and stores it as a cached value, so subsequent queries can retrieve the pre-computed result without re-evaluating the function, thus maintaining data relationship integrity while improving query performance
Solution Approach 2:
The patent uses copying by creating and storing copies of computed function results alongside the original data entries. Instead of repeatedly evaluating functions during queries, the system maintains cached copies of function outputs that can be quickly retrieved, reducing the computational overhead of function evaluation while preserving the ability to access updated values when source data changes
Data Source
AI summary
A system and method for improving the performance of an issue management system is disclosed. The system includes a server communicating with an issue management database and a client running on a remote device such as a mobile phone. The client provides a user interface for making queries of the issue management database. Users can select filtering parameters to narrow the query space. Upon receiving a user query the system can request information from server and the issue management database related to the query and the filtering parameters. Using the response from the server and database the client can build a partial database that is stored locally. Further user queries are performed on the partial database rather than the full server-side database to enhance performance and response time of the system.