Hybrid Cloud Integration via Queue-Based Feedback Loop
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating cloud computer systems with backend systems is challenging due to differences in computing environments, data formats, and process flows, leading to performance degradation and error management issues, particularly when moving data between systems.
Innovation Solution
Implementing a hybrid cloud integration system that uses a feedback loop with request, acknowledgement, and confirmation messages to coordinate data processing between cloud and backend systems, storing data in a queue to prevent performance degradation and allowing asynchronous operation, with data locked until confirmation of processing completion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If backend system runs queries against cloud transactional database, then data can be accessed, but cloud database performance degrades
Solution Approach 1:
The patent extracts data from the cloud transactional database into a separate queue structure. When the backend system needs data, it queries the queue rather than the transactional database. This separation removes the burden of backend queries from the cloud database, maintaining its performance while still enabling data access through the queue mechanism.
Solution Approach 2:
The patent introduces a queue as an intermediary layer between the cloud transactional database and the backend system. The queue acts as a buffer that decouples the database from backend queries, allowing the database to operate independently without performance degradation from backend access patterns.
2Productivity
If data is moved to backend system for processing, then processing can be distributed, but error tracking becomes difficult
Solution Approach 1:
The patent implements a feedback mechanism where the backend system sends acknowledgment messages back to the cloud system when data is received and processed. This feedback loop includes status information that allows the cloud system to track whether backend processing succeeded or failed, maintaining visibility despite distributed processing.
Solution Approach 2:
The patent uses a queue with locking mechanisms that prepare and stage data before backend processing. Data is placed in the queue with associated metadata and status flags that track its processing state. This preliminary organization ensures that error tracking information is preserved and accessible throughout the processing workflow.
3Reliability
If cloud system waits for backend confirmation, then data integrity is ensured, but processing time increases
Solution Approach 1:
The patent implements periodic polling or asynchronous confirmation mechanisms where the cloud system checks for backend processing status at intervals rather than waiting continuously. The queue system allows the cloud system to proceed with other operations while periodically checking for confirmations, reducing idle waiting time while maintaining data integrity through eventual consistency.
Data Source
AI summary
In one embodiment, first and second computer systems are integrated to exchange information and coordinate processing of data. A first computer system may access data in a database for a document ready for external processing. The data may be stored in a queue and retrieved by the second system using a request. The second system sends an acknowledgement when the data is received. The data in the queue may be locked until a confirmation is received in the first system that processing on the second system is complete. In particular embodiments, the first system may be a cloud computer system and the second system a backend computer system.