View source for 17986292. DETECTING IMPACT OF API USAGE IN MICROSERVICES simplified abstract (INTERNATIONAL BUSINESS MACHINES CORPORATION)

=DETECTING IMPACT OF API USAGE IN MICROSERVICES=


==Organization Name==

[[:Category:INTERNATIONAL BUSINESS MACHINES CORPORATION|INTERNATIONAL BUSINESS MACHINES CORPORATION]]


[[Category:INTERNATIONAL BUSINESS MACHINES CORPORATION]]

==Inventor(s)==

[[:Category:Rei Odaira of Austin TX (US)|Rei Odaira of Austin TX (US)]][[Category:Rei Odaira of Austin TX (US)]]

[[:Category:Bedri Sendir of Austin TX (US)|Bedri Sendir of Austin TX (US)]][[Category:Bedri Sendir of Austin TX (US)]]

[[:Category:Prawar Poudel of Morang (NP)|Prawar Poudel of Morang (NP)]][[Category:Prawar Poudel of Morang (NP)]]

==DETECTING IMPACT OF API USAGE IN MICROSERVICES - A simplified explanation of the abstract==


This abstract first appeared for US patent application 17986292 titled 'DETECTING IMPACT OF API USAGE IN MICROSERVICES

==Simplified Explanation==

The computer hardware system described in the abstract includes a static analyzer, a load estimator, and a hardware processor. The system analyzes egress API call sites associated with an ingress API handler of a microservice, generates weights for each site, estimates the load based on these weights, and modifies the microservice accordingly.

* Static analyzer generates weights for egress API call sites
* Load estimator determines load based on weights and call frequency
* Hardware processor modifies microservice based on load analysis

== Potential Applications ==
The technology can be applied in:
* Cloud computing
* Microservices architecture
* Performance optimization in software development

== Problems Solved ==
This technology addresses issues such as:
* Overloaded API endpoints
* Inefficient resource allocation
* Poor performance of microservices

== Benefits ==
The benefits of this technology include:
* Improved scalability
* Enhanced performance
* Efficient resource utilization

== Potential Commercial Applications ==
The technology can be commercially benefit:
* Cloud service providers
* Software development companies
* IT consulting firms

== Possible Prior Art ==
One possible prior art could be:
* Load balancing algorithms in distributed systems

== Unanswered Questions ==

=== How does the system handle dynamic changes in load over time? ===
The system likely utilizes real-time monitoring and adjustment mechanisms to adapt to changing load conditions.

=== What impact does the modification of the microservice have on overall system performance? ===
The modification of the microservice based on load analysis could potentially improve system performance by optimizing resource allocation and reducing bottlenecks.


==Original Abstract Submitted==

A computer hardware system includes a static analyzer, a load estimator, and a hardware processor configured to perform the following executable operations. Using the static analyzer and for each egress API call site respectively associated with an ingress API handler of a microservice, a weight is generated and is included within a static analysis of the microservice also generated by the static analyzer. Using the load estimator and for each of the egress API call sites, a load is determined based upon the weight for the egress API call site, a number of times, over a predetermined period of time, a particular ingress API handler associated with the egress API call site is called, and a cost of a call to the egress API call site. Based upon the load, the microservice is modified.



[[Category:G06F9/54]]