Synchronous Atomic Updates in Non-Relational Databases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Ensuring timely processing of user requests and maintaining system consistency across diverse hardware and software platforms in remote computing environments is challenging, especially when dealing with non-transactional databases and asynchronous workflows.
Innovation Solution
Implementing a system that initiates synchronous atomic updates in non-relational databases for immediate response and queues asynchronous workflows for computationally intensive operations, utilizing virtual computing engines and asynchronous services to manage and execute tasks, ensuring overall system consistency and minimizing user wait times.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If synchronous processing is used for all operations, then system consistency is maintained, but user wait time increases
Solution Approach 1:
The patent segments database operations into two distinct categories: synchronous operations for immediate response (e.g., atomic updates to non-relational databases) and asynchronous operations for background processing (e.g., computationally intensive tasks). This segmentation allows the system to maintain consistency for critical operations while eliminating wait time for non-critical operations by processing them in the background.
Solution Approach 2:
The patent changes the processing parameter from synchronous to asynchronous for specific operations. By introducing an asynchronous service that processes tasks in the background and notifies completion via callbacks or polling, the system transforms the time-characteristic of operations, allowing immediate response for critical path operations while background processing for others.
2Loss of time
If asynchronous workflows are used for all operations, then user wait time is reduced, but system consistency becomes difficult to ensure
Solution Approach 1:
The patent segments operations into synchronous and asynchronous categories based on consistency requirements. Synchronous operations (e.g., atomic database updates) maintain immediate consistency, while asynchronous operations (e.g., document processing) accept delayed consistency with eventual consistency guarantees. This segmentation resolves the contradiction by applying different consistency models to different operations.
Solution Approach 2:
The asynchronous service incorporates feedback mechanisms where the system notifies clients of task completion through callbacks or polling. This feedback loop ensures that clients are aware of the final state of asynchronous operations, providing a form of consistency assurance even though the operations themselves execute in the background.
3Speed
If non-transactional databases are used, then processing speed increases, but data consistency and reliability decrease
Solution Approach 1:
The patent segments database operations into atomic operations for non-relational databases (which provide fast, single-point consistency) and handles multi-point consistency through asynchronous workflows. The asynchronous service coordinates multiple atomic operations to achieve overall system consistency without requiring transactional guarantees at the database level, thus maintaining high speed while achieving necessary reliability.
Data Source
AI summary
A method and apparatus for processing service requests for non-transactional databases are disclosed. In the method and apparatus, the execution of a first operation may be initiated based at least in part on receiving a service request from a user. The first operation may be executed synchronously with receipt of the request. Further, one or more execution workflows may be provisioned for asynchronous execution of one or more other operations.