System and method for graph based K-redundant resiliency for IT cloud
US-9143394-B2 · Sep 22, 2015 · US
US10810112B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10810112-B2 |
| Application number | US-201816028921-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 6, 2018 |
| Priority date | Aug 5, 2016 |
| Publication date | Oct 20, 2020 |
| Grant date | Oct 20, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Techniques are provided for automated resiliency testing. In one example, a computer-implemented method comprises analyzing, by a system operatively coupled to a processor, an annotated state transition graph of a user interface of a microservices-based application, wherein the annotated state transition graph has edges annotated with application program interface call subgraphs. The computer-implemented method also comprises generating, by the system, an ordered list of the application program interface call subgraphs based on the analyzing.
Opening claim text (preview).
What is claimed is: 1. A system, comprising: a memory that stores computer executable components; and a processor that executes the computer executable components stored in the memory, wherein the computer executable components comprise: a prioritization component that generates an ordered list of application program interface call subgraphs associated with a user interface of a microservices-based application, wherein the application program interface call subgraphs are ordered based on respective failure impact values of the application program interface call subgraphs, wherein a failure impact value of the respective failure impact values indicates a determined impact on at least one functionality of the microservices-based application in response to a failure of at least one application program interface of an application program interface call subgraph associated with the failure impact; and a test execution component that iteratively performs in the order of the ordered list for respective application program interface call subgraphs of a subset of application program interface call subgraphs: based on at least one resiliency test pattern, generation of at least one failure scenario for an application program interface call subgraph of the subset of application program interface call subgraphs; and test of the application program interface call subgraph for the at least one resiliency pattern using the at least one failure scenario. 2. The system of claim 1 , wherein the prioritization component generates the ordered list based on a state transition graph associated with the user interface, wherein state transition graph comprises nodes respectively representing abstract user interface states of the user interface and edges respectively representing transitions between the abstract user interface states resulting from user interface events triggered from the user interface states. 3. The system of claim 2 , further comprising: a user interface crawling component that traverses the user interface based on the state transition graph and triggers the user interface events from the user interface states; and a state transition graph component that: determines the application program interface subgraphs based on an analysis of one or more logs generated based on the traversing the user interface; and annotates respective edges of the state transition graph with application program interface call subgraphs associated with user interface events that resulted in the transitions associated with the edges to generate an annotated state transition graph. 4. The system of claim 1 , wherein the prioritization component orders the application program interface call subgraphs in descending order of the respective failure impact values. 5. The system of claim 1 , wherein the test execution component tests nodes of the application program interface call subgraph according to a systematic resilience testing process that reduces redundant resiliency testing of application program interfaces of the application program interface call subgraph. 6. The system of claim 1 , wherein the test execution component determines a subset of application program interface call subgraphs based on an amount of time available prior to deployment of the microservices-based application in a live environment. 7. The system of claim 6 , wherein the test execution component transmits a recommendation to at least on recipient indicating whether to deploy the microservices-based application in a live environment, and wherein the recommendation is determined based on an analysis of results of the tests of the subset of application program interface call subgraphs for the at least one resiliency pattern. 8. A computer-implemented method, comprising: analyzing, by a system operatively coupled to a processor, an annotated state transition graph of a user interface of a microservices-based application, wherein the annotated state transition graph has edges annotated with application program interface call subgraphs, and the edges are assigned respective failure impact values, wherein a failure impact value of the respective failure impact values indicates a determined impact on the microservices-based application in response to a failure of at least one application program interface of an application program interface call subgraph associated with an edge to which the failure impact value is assigned; and generating, by the system, an ordered list of the application program interface call subgraphs based on the respective failure impact value assigned to the edges. 9. The computer-implemented method of claim 8 , wherein the analyzing further comprises traversing, by the system, a state transition graph of the user interface of the microservices-based application. 10. The computer-implemented method of claim 9 , wherein the analyzing further comprises merging, by the system, a user interface event log and one or more server-side request logs generated during the traversing into an aggregated log. 11. The computer-implemented method of claim 10 , wherein the analyzing further comprises: identifying, by the system, in the aggregated log, respective user interface events that trigger the application program interface call subgraphs; and annotating, by the system, edges of the state transition graph corresponding to the user interface events with the triggered associated application program interface call subgraphs to generate the annotated state transition graph. 12. The computer-implemented method of claim 11 , wherein the analyzing further comprises assigning, by the system, the respective failure impact values to the edges based on one or more failure impact criterion. 13. The computer-implemented method of claim 12 , wherein the generating the ordered list of the application program interface call subgraphs is further based on the respective failure impact values and one or more ordering criterion. 14. The computer-implemented method of claim 12 , wherein the generating the ordered list of the application program interface call subgraphs further comprises merging, by the system, one or more adjacent application program interface call subgraphs in the ordered list based on one or more merging criterion. 15. A computer program product for prioritizing application program interface call subgraphs associated with a user interface of a microservices-based application for resiliency testing, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processing component to cause the processing component to: analyzing an annotated state transition graph of the user interface of the microservices-based application, wherein the annotated state transition graph has edges annotated with application program interface call subgraphs, and the edges are assigned respective failure impact values, wherein a failure impact value of the respective failure impact values indicates a determined impact on the microservices-based application in response to a failure of at least one application program interface of an application program interface call subgraph associated with an edge to which the failure impact value is assigned; and generating an ordered list of the application program interface call subgraphs based on the respective failure impact value assigned to the edges. 16. The computer program product of claim 15 , wherein the analyzing further comprises traversing a state transition graph of the user interface of the microservices-based applic
Performance evaluation by tracing or monitoring · CPC title
where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title
Visualisation of programs or trace data · CPC title
Monitoring of software · CPC title
where the computing system component is a software system · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.