Automatically setting a dynamic restore policy in a native cloud environment
AssigneeEMC IP Holding Company LLC
InventorsLuay Al-Alem, Antony Bett, Assaf Natanzon, Michael Rhodes
Life of this patent
Estimating the term…
Abstract
One example method includes receiving an indication that an application has experienced a problem, where the application comprises a plurality of microservices, discovering that one of the microservices is a partial cause of the problem, identifying one or more connections among the microservices, where one or more of the connections indicates a dependency, or lack of dependency, among two or more microservices, and restoring the microservice that is a partial cause of the problem, and also restoring any other microservices that are dependent on that microservice.
Claims20
A method, comprising:
- receiving an indication that an application has experienced a problem, where the application comprises a plurality of microservices;
- discovering that one of the microservices is a partial cause of the problem;
- identifying one or more connections among the microservices, where one or more of the connections indicates a dependency, or lack of dependency, among two or more microservices;
- and
- restoring, together, both the microservice that is a partial cause of the problem and any other microservices that are dependent on that microservice.
A non-transitory storage medium having stored therein computer-executable instructions which, when executed by one or more hardware processors, perform the following operations:
- receiving an indication that an application has experienced a problem, where the application comprises a plurality of microservices;
- discovering that one of the microservices is a partial cause of the problem;
- identifying one or more connections among the microservices, where one or more of the connections indicates a dependency, or lack of dependency, among two or more microservices;
- and
- restoring, together, both the microservice that is a partial cause of the problem and any other microservices that are dependent on that microservice.
Dependencies are inferred from the claim text.