Idempotent Check via Reference Information in Sharded Databases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed storage and disaster recovery scenarios, idempotent failures occur due to requests being routed to different data tables, leading to repeated service processing in database sharding and partitioning applications, where existing solutions fail to ensure idempotence across different storage locations.
Innovation Solution
Incorporating service processing reference information into service requests to determine the correct storage location for idempotent checks, ensuring that repeated requests for the same service event include the same reference information, thereby performing idempotent checks on the same storage location and preventing repeated processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored through partition or sharding in distributed storage scenarios, then storage capacity and system availability are improved, but idempotence of service requests cannot be ensured across different data tables
Solution Approach 1:
The patent applies segmentation by dividing the idempotency check mechanism into two parts: the service request side generates and retains service processing reference information, while the service processing side performs idempotency checks using this information. This segmentation allows each side to have independent functionality while maintaining overall system idempotence across partitioned or sharded data tables.
Solution Approach 2:
The service processing reference information acts as an intermediary element that bridges the service request side and service processing side. This intermediary carries the necessary identification data across different data tables and storage locations, enabling consistent idempotency verification without requiring complex coordination between distributed storage components.
2Productivity
If service requests are routed to different data tables for disaster recovery or partitioning, then system availability is improved, but repeated service processing occurs due to idempotent failures
Solution Approach 1:
The patent applies preliminary action by having the service request side generate and retain service processing reference information before the service is actually processed. This pre-prepared reference information is then available for idempotency checks regardless of which data table or storage location handles the request, preventing repeated processing even when requests are routed to different tables for disaster recovery or partitioning.
Solution Approach 2:
The service processing reference information serves as a feedback mechanism that provides consistent identification data back to the service processing side across multiple requests. This feedback loop enables the system to verify whether a service has already been processed, even when routed to different data tables, thereby preventing duplicate operations while maintaining high system availability.
Data Source
AI summary
A service processing device receives a service processing request for a service event sent by a service requesting device, where the service processing request comprises service processing reference information, and where the service processing reference information is used by the service processing device to determine a storage location of data related to a current service in a database. A particular storage location is determined based on the service processing reference information. An idempotent check is performed on the particular storage location. A method of processing is determined to perform on the current service based on a result of the idempotent check.