Database Triggered Push Notification for Cached Data Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 'Big Data' environments, managing voluminous and complex data efficiently is challenging due to the risk of data inconsistency caused by dynamic database entities, which requires frequent refreshing of cached data to maintain consistency but increases system load.
Innovation Solution
Implementing a database triggered push notification mechanism that sends messages to affected sessions when database entities are altered, allowing for selective refresh of cached data and minimizing unnecessary synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If cached database entities are re-checked frequently to minimize data inconsistency risk, then data consistency is improved, but system load increases
Solution Approach 1:
The patent implements a feedback mechanism where database triggers automatically detect changes in database entities and send notifications to cached data holders. This feedback loop eliminates the need for frequent polling by providing real-time change information, thus maintaining data consistency without increasing system load through continuous checking
Solution Approach 2:
The database system performs self-service by automatically detecting its own changes through triggers and proactively notifying affected components. This eliminates the need for external components to continuously query and check for changes, reducing the overall system load while maintaining reliability
2Reliability
If cached data is refreshed frequently to maintain consistency with dynamic database entities, then data consistency is improved, but resource consumption increases
Solution Approach 1:
The patent applies preliminary action by setting up database triggers in advance that automatically detect changes as they occur. This preliminary detection mechanism ensures that cached data is refreshed only when necessary, avoiding unnecessary resource consumption from frequent scheduled refreshes while maintaining data consistency
3Reliability
If all cached data is synchronized frequently to ensure consistency, then data consistency is improved, but system efficiency deteriorates
Solution Approach 1:
The patent segments the cached data into specific entities and uses database triggers to identify which specific entities have changed. This segmentation allows for selective refreshing of only the affected cached entities rather than synchronizing all cached data, thereby maintaining consistency while improving system efficiency
Solution Approach 2:
The patent applies local quality by providing different refresh behaviors to different cached entities based on whether they are affected by database changes. Only the locally affected cached entities are refreshed, while unaffected entities remain unchanged, optimizing system efficiency while maintaining necessary data consistency
Data Source
AI summary
Systems and methods of database triggered push notification are disclosed. In one aspect, data from a database entity is cached in response to executing user service request at a client session, where the service request involves information from the database entity. In response to caching the data from the database entity, the client session subscribing to a messaging channel dedicated to the database entity. In another aspect, a message is generated as a result of invoking a trigger by an operation in the database entity. In yet another aspect, the message is transported by the messaging channel to the subscribed client session to invoke refresh of the cached data. A push notification is sent to the client in response to the message.