Atomicity Assurance for Collaborative Services via Cancellation API
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing collaborative service execution apparatuses lack a mechanism to secure atomicity, leading to loss of atomicity when one service in a group of services fails, as they do not properly handle the cancellation of processes for other services that have completed updates.
Innovation Solution
An atomicity securing apparatus that determines if processes for other services are completed upon an error response, generates and transmits cancellation API requests to cancel these processes, and generates state reports to revert the collaborative services to a pre-execution state, using a service cancellation information storage unit to manage cancellation mechanisms for various APIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the collaborative service execution apparatus interrupts execution of collaborative services when an API replies with an error response, then execution continuity is maintained, but atomicity of the collaborative services is lost when other services have already completed updates
Solution Approach 1:
The patent applies preliminary action by establishing a booking mechanism before executing collaborative services. The system books update processes for all services in advance, recording their states before execution. When an error occurs, this pre-established booking information enables systematic rollback without complex real-time coordination, as the cancellation paths were prepared in advance.
Solution Approach 2:
The patent implements feedback by continuously monitoring the execution state of each service in the collaborative group. When an error response is received from any API, the system uses feedback from the booking mechanism to determine which services need rollback. The state report generation unit provides feedback about the rollback progress, ensuring atomicity is maintained through closed-loop control.
2Productivity
If the system allows services to complete updates before detecting errors, then execution efficiency is improved, but atomicity cannot be secured when failures occur
Solution Approach 1:
The booking mechanism performs preliminary registration of all services before execution begins. This allows the system to proceed with execution efficiently while having the atomicity guarantee structure already in place. The preliminary booking does not hinder execution speed but enables post-error atomicity recovery.
Solution Approach 2:
The system prepares cancellation mechanisms in advance for each booked service. This beforehand cushioning ensures that if any service completes updates before an error is detected, the rollback path is already prepared, preventing atomicity loss without requiring slow synchronous verification during execution.
3Reliability
If the system implements a rollback mechanism for all services when an error occurs, then atomicity is maintained, but the complexity of handling different cancellation methods for various services increases
Solution Approach 1:
The booking mechanism serves multiple functions: it records service states, tracks execution progress, and stores cancellation information for diverse services. This universal mechanism handles different service types and cancellation methods through a unified interface, reducing the apparent complexity while maintaining atomicity across heterogeneous services.
Solution Approach 2:
The booking mechanism acts as an intermediary layer between the error detection system and the diverse service cancellation mechanisms. Instead of directly managing complex service-specific rollback procedures, the system uses the booking mechanism to coordinate cancellations, simplifying the overall control logic while ensuring atomicity.
4Reliability
If the system checks the completion status of all services upon error, then atomicity can be restored, but the time required to detect and respond to errors increases
Solution Approach 1:
The booking mechanism records completion status information in advance during service execution. When an error occurs, the system can immediately query this pre-recorded information rather than checking service states from scratch, significantly reducing the time required to determine which services need rollback while ensuring accurate atomicity restoration.
Data Source
AI summary
An atomicity securing apparatus that secures atomicity of collaborative services includes: an atomicity determination unit configured to determine, in a case in which there is an error response to a first service among a plurality of types of services configuring the collaborative services in response to a request to execute the plurality of types of services, whether or not a process for updating second services other than the first service in the plurality of types of services is completed in consideration of inquiry to a collaborative service execution apparatus that executes the collaborative services; a cancellation API request generation unit configured to generate a cancellation API request for canceling the process for updating the second services that is completed; and a cancellation API request transmission unit configured to transmit the generated cancellation API request to a server that provides the second services.