Middle-Tier Platform for Unified Backend Access and Delay Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise-level organizations face challenges in providing seamless and unified access to independent backend processing systems, which often experience processing delays and downtime, requiring a robust middle-tier platform to coordinate requests and manage intermediary processing tasks.
Innovation Solution
A middle-tier platform that receives API method calls, writes parameters to a datastore with batch fields, executes intermediary processing procedures, and makes secondary API calls to backend systems, ensuring non-volatile storage and handling of processing delays through batch processing and lock flags.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a middle-tier platform is introduced to coordinate processing requests across independent backend systems, then unified access and coordination capability are improved, but system complexity increases
Solution Approach 1:
The patent implements a middle-tier platform that serves as an intermediary layer between front-end users and multiple independent backend systems. This platform provides unified access points and coordinates processing requests across disparate systems, thereby improving adaptability and unified access capability while managing the inherent system complexity through structured mediation
2Reliability
If batch processing is implemented to handle processing delays, then handling of delayed requests is improved, but processing time increases
Solution Approach 1:
The patent implements batch processing as a periodic action mechanism that collects and processes delayed requests in scheduled batches. This approach improves reliability by ensuring that delayed requests are systematically handled, while the periodic nature allows for optimized processing intervals that balance completeness with time efficiency
3Reliability
If non-volatile storage is used to maintain request state during interruptions, then reliability during downtime is improved, but storage requirements increase
Solution Approach 1:
The patent extracts and persists only the essential request state information to non-volatile storage, rather than storing complete request contexts. This selective extraction maintains reliability during backend downtime by preserving critical state data, while minimizing storage requirements by storing only what is necessary for state recovery
Data Source
AI summary
In some aspects, the techniques described herein relate to a method including: receiving, at an application programming interface (API) of a middle-tier platform, an initial API method call including a request identifier associated with a processing request and a data parameter; writing the data parameter and the request identifier to a record of a datastore, wherein the record of the datastore includes a batch field; writing a value of false to the batch field; executing, by a first intermediary processing procedure, a query of the datastore, wherein the query of the datastore retrieves the record of the datastore; performing, by a second intermediary processing procedure, additional intermediary processing; making a secondary API call to a backend system; receiving a second data parameter from the backend system in response to the secondary API call; and generating a response to the processing request.