Common Instance Handler for Multi-Provider Data Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enterprise services architectures, interference between multiple providers can result in data inconsistencies and corruption when operating on business objects, making it difficult to manage and often leading to errors that cannot be undone or propagated through the database.
Innovation Solution
A common instance handler is introduced to register changes from multiple providers to a buffer, check for data consistency, and commit changes only when consistency is guaranteed, using a method that includes registering instances of providers, checking the buffer for inconsistencies, and committing changes when consistency is ensured.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple providers are allowed to operate on business objects simultaneously, then system functionality and productivity are improved, but data consistency and reliability deteriorate due to runtime interference
Solution Approach 1:
The patent introduces a buffer as an intermediary component between multiple providers and the database. The buffer temporarily stores changes from multiple providers before committing them to the database, allowing simultaneous operations while maintaining data consistency. The buffer acts as a mediator that coordinates changes from different providers and ensures they don't interfere with each other.
Solution Approach 2:
The patent implements preliminary consistency checking of the buffer before committing changes to the database. This preliminary action verifies that data consistency will be maintained before the actual commit occurs, preventing inconsistent states from being propagated to the database while still allowing multiple providers to operate simultaneously.
2Productivity
If changes from multiple providers are committed to the database, then system productivity is improved, but data corruption and errors increase due to runtime interference
Solution Approach 1:
The buffer serves as a protective intermediary that isolates the database from direct simultaneous writes by multiple providers. By funneling all changes through the buffer and performing consistency checks before database commits, the system maintains high throughput while preventing data corruption at the database level.
Solution Approach 2:
The system performs beforehand cushioning by checking buffer consistency before committing changes to the database. This preventive measure cushions against potential data corruption by detecting and preventing inconsistent states before they reach the database, thereby protecting against data corruption while maintaining productivity.
3Reliability
If a common instance handler is introduced to manage provider instances, then data consistency is improved, but device complexity increases
Solution Approach 1:
The common instance handler is designed as a universal component that manages instances across multiple frameworks and providers. By creating a single multi-functional handler that can manage any provider instance from any framework, the system improves data consistency without proportionally increasing complexity, as one component serves multiple purposes.
Solution Approach 2:
The patent merges the instance management functionality into a single common instance handler that consolidates responsibilities for tracking and coordinating provider instances across different frameworks. This merging reduces overall system complexity compared to having separate management mechanisms for each framework while maintaining improved data consistency.
Data Source
AI summary
Systems and methods are provided for handling instances of providers in a plurality of frameworks. An instance of a first provider is created and registered to store a first change to a buffer. An instance of a second provider is created and registered to store a second change to the buffer. The buffer is checked to determine whether data consistency is guaranteed to result from the first and second changes. If data consistency is guaranteed, the first and second changes are committed to a database.