Dell products l.p. (20240338260). MECHANISM TO DETECT AND SUGGEST MORE EFFICIENT REST API END POINTS simplified abstract
Contents
MECHANISM TO DETECT AND SUGGEST MORE EFFICIENT REST API END POINTS
Organization Name
Inventor(s)
Aaron T. Twohig of Rathpeacon (IE)
MECHANISM TO DETECT AND SUGGEST MORE EFFICIENT REST API END POINTS - A simplified explanation of the abstract
This abstract first appeared for US patent application 20240338260 titled 'MECHANISM TO DETECT AND SUGGEST MORE EFFICIENT REST API END POINTS
The abstract describes a method where a computing system receives a single-action API call associated with a specific operation from a sender. The system then determines if the API call is part of a burst by checking if multiple API calls related to the same operation have been received within a set time frame. If it is part of a burst, an error message is generated and sent back to the sender. If not, the API call is executed.
- The method involves receiving single-action API calls and detecting bursts of related calls.
- Error messages are generated and sent back to the sender in case of bursts.
- The system executes the API call if it is not part of a burst.
Potential Applications: - This method can be used in systems handling high volumes of API calls to prevent overload and ensure smooth operation. - It can be applied in cloud computing environments to manage and prioritize API requests effectively.
Problems Solved: - Prevents system overload by detecting and handling bursts of API calls. - Ensures the efficient execution of API requests in high-demand scenarios.
Benefits: - Improved system performance and reliability. - Enhanced scalability and resource management in computing environments.
Commercial Applications: Title: "Efficient API Call Management System for High-Traffic Environments" This technology can be valuable for cloud service providers, online platforms, and any system dealing with a large number of API requests. It can optimize resource utilization and enhance overall performance, leading to better user experience and cost savings.
Questions about API Call Burst Detection: 1. How does the system determine if a group of API calls constitutes a burst? The system checks if multiple API calls related to the same operation are received within a predetermined time window to identify bursts.
2. What are the potential consequences of not detecting and handling bursts of API calls efficiently? Failure to manage bursts of API calls can lead to system overload, performance degradation, and potential service disruptions.
Original Abstract Submitted
a method, comprising: receiving, at a computing system, a given single-action api call, the given single-action api call being transmitted by a sender, the given single-action api call being associated with a given operation; detecting whether the given single-action api call is part of a burst, wherein detecting whether the given single-action api call is part of the burst includes detecting whether a plurality of single-action api calls that are associated with the given operation have been received from the sender of the given single-action api call in a predetermined time window; when the given single-action api call is part of a burst, generating an error message in response to the given single-action api call and returning the error message to the sender of the given single-action api call; and when the given single-action api call is not part of a burst, executing the given single-action api call.
