Master Data Consistency via Update Flagging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In loosely-coupled cloud applications, ensuring data consistency of master data across multiple applications is challenging due to network-based threats and the potential for outdated data to be processed during updates, leading to inconsistencies and errors.
Innovation Solution
Implementing a flag system to indicate when an update process is running, denying access to affected master data objects and using unique identifiers for data tracking to prevent outdated data from being processed, ensuring that only the latest version is used.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If master data updates are processed in a queue-based middleware system, then data distribution efficiency is improved, but data consistency deteriorates due to potential processing of outdated data
Solution Approach 1:
The system sets update flags on master data objects before the actual update is applied. This preliminary action prevents other processes from reading outdated data by marking it as being updated, ensuring that even if data is queued for update, no process can inadvertently use stale information until the update is complete.
Solution Approach 2:
The system implements a feedback mechanism where update flags are set and cleared based on the state of the update queue. When updates are present in the queue, flags are set to prevent reads; when the queue is empty, flags are cleared to allow normal operations. This feedback loop maintains data consistency while allowing efficient batch processing.
2Reliability
If multiple updates to the same master data object are queued, then update completeness is improved, but access efficiency deteriorates due to denied access during updates
Solution Approach 1:
Update flags are set immediately when an update is queued, before the actual data modification occurs. This ensures that even if multiple updates are queued sequentially, the flag remains set throughout the entire update process, preventing any intermediate reads of partially updated data while maintaining a clear indication of the update state.
Solution Approach 2:
The update flag state dynamically changes based on the presence of queued updates. The flag is set when updates are queued and cleared when the queue is processed, allowing the system to adapt its access control behavior to the current update state. This dynamic approach balances consistency requirements with access efficiency.
Data Source
AI summary
An update system may be used to update referenced data objects that are used by multiple applications. In some cases incorrect data may be entered and later corrected. Data consistency techniques are described herein to help avoid use of incorrect data before the data is corrected. A communication from the update system may include updated master data objects and an indication that there are further updates queued. A flag may be set for each of the updated master data objects as they are stored in a database. Then when a request to access those objects is received, the request may be denied when the flag set, thereby preventing access to potentially incorrect or outdated data.