Cached API Data Force-Supply for Order Processing Failures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems experience outages or errors when processing order requests, leading to re-examination of order requests with changed variables, resulting in rejections that degrade user experience, increase bandwidth and processing loads, and require duplicate computations, especially for discount information.
Innovation Solution
A system and method for force-supplying cached API call data by receiving initial order data, determining an initial reduction amount, mapping it to a cache identifier, caching the data, detecting API failures, retrieving the cache identifier, and completing the order request using a final reduction amount, which may be based on the cached data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the system re-examines order requests after API outages to check for changed variables, then reliability of order processing is improved, but processing time and system load increase
Solution Approach 1:
The system performs preliminary actions by caching order request data and discount information before API outages occur. When an outage happens, the cached data is already prepared and can be quickly retrieved without re-examination, thus maintaining reliability while reducing processing time during failure scenarios.
Solution Approach 2:
The patent applies local quality by selectively caching only the most frequently accessed or critical order request data and discount information, rather than caching everything. This targeted approach reduces the overall data volume to be managed while ensuring that essential information is available during outages, balancing reliability improvements with processing efficiency.
2Measurement precision
If the system re-examines order requests after API outages, then accuracy of discount information is improved, but computational resources are depleted
Solution Approach 1:
The system pre-calculates and caches discount information and order request details before API failures occur. This preliminary computation ensures accuracy is maintained while avoiding the need to re-perform complex calculations during outages, thus preserving computational resources when they are most needed for other operations.
Solution Approach 2:
The patent creates copies of order request data and discount information in a cached format. These copies maintain the accuracy of the original data while requiring minimal computational resources to retrieve and process, allowing the system to handle multiple simultaneous requests efficiently without depleting computational resources.
3Reliability
If the system processes order requests with duplicate computations during outages, then completeness of order data is improved, but system responsiveness deteriorates
Solution Approach 1:
The system performs preliminary actions by pre-processing and caching complete order request data including all necessary discount calculations before outages occur. During failures, this pre-prepared data can be quickly retrieved and applied, ensuring data completeness is maintained while restoring system responsiveness that would otherwise be degraded by duplicate computations.
Data Source
AI summary
Systems and methods for force-supplying cached API call data are disclosed. A system may comprise a memory storing instructions and at least one processor configured to execute instructions to perform operations including: receiving initial order data from a user device, the initial order data comprising a product identifier, a user identifier, and a promotion identifier; determining an initial reduction amount based on the received product identifier and promotion identifier; mapping the initial reduction amount to a cache identifier; caching the initial order data and the cache identifier; receiving an order request from a device associated with the user identifier, the order request being associated with the promotion identifier; calling an API to complete the order request; detecting a failure of the API attempting to complete the order request; retrieving the cache identifier; determining a final reduction amount; and completing the order request using the final reduction amount.