18296512. MECHANISM TO DETECT AND SUGGEST MORE EFFICIENT REST API END POINTS simplified abstract (Dell Products L.P.)

From WikiPatents
Revision as of 02:46, 18 October 2024 by Wikipatents (talk | contribs) (Creating a new page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

MECHANISM TO DETECT AND SUGGEST MORE EFFICIENT REST API END POINTS

Organization Name

Dell Products L.P.

Inventor(s)

Paul Mcsweeney of Cork (IE)

Aaron T. Twohig of Rathpeacon (IE)

Aidan Hally of Fermoy (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 18296512 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 part of a burst, the API call is executed.

  • The method involves receiving single-action API calls and detecting bursts of such calls.
  • It includes generating error messages for burst API calls and executing non-burst API calls.
  • The system tracks the frequency of API calls related to the same operation to determine bursts.
  • This method helps in managing and controlling the flow of API calls to prevent system overload.
  • By identifying bursts of API calls, the system can prioritize and handle them efficiently.

Potential Applications: - This technology can be applied in systems where there is a high volume of API calls to prevent overload. - It can be used in cloud computing environments to optimize resource allocation based on API call patterns.

Problems Solved: - Prevents system overload by managing bursts of API calls effectively. - Ensures smooth operation of systems by prioritizing and handling API calls efficiently.

Benefits: - Improved system performance and stability. - Enhanced resource allocation in cloud computing environments. - Better control and management of API call traffic.

Commercial Applications: Title: "Optimizing API Call Management for Enhanced System Performance" This technology can be utilized in cloud service providers, SaaS companies, and any organization dealing with a large number of API calls to improve system efficiency and performance.

Prior Art: Further research can be conducted in the field of API call management systems to explore similar methods and technologies used in handling bursts of API calls.

Frequently Updated Research: Stay updated on advancements in API call management systems, cloud computing optimization, and resource allocation strategies to enhance system performance.

Questions about API Call Burst Management: 1. How does this method help in preventing system overload caused by bursts of API calls? - This method tracks the frequency of API calls related to the same operation to identify bursts and manage them effectively, preventing system overload. 2. What are the potential applications of this technology beyond managing API call bursts? - This technology can also be applied in optimizing resource allocation in cloud computing environments and improving overall system performance.


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.