Automatically setting a dynamic restore policy in a native cloud environment

Patent metadata

Field	Value
Publication number	US-10853180-B2
Application number	US-201816155789-A
Country	US
Kind code	B2
Filing date	Oct 9, 2018
Priority date	Oct 9, 2018
Publication date	Dec 1, 2020
Grant date	Dec 1, 2020

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.

First claim

What is claimed is:

1. 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.

2. The method as recited in claim 1 , wherein identifying one or more connections comprises consulting microservice dependency information that was created prior to occurrence of the problem, and the microservice dependency information discloses the one or more connections.

3. The method as recited in claim 1 , wherein one of the microservices comprises an element of another application.

4. The method as recited in claim 1 , wherein identifying one or more connections among the microservices comprises evaluating a service mesh that includes connection information.

5. The method as recited in claim 1 , wherein at least part of the method is performed automatically without human instruction or human intervention.

6. The method as recited in claim 1 , wherein the restoration process is performed automatically as a result of receipt of the indication that a problem has occurred.

7. The method as recited in claim 1 , wherein the method is performed in a cloud computing environment.

8. The method as recited in claim 1 , wherein the restoring is performed according to a policy that was created based on dependency information that discloses the connections among the microservices.

9. The method as recited in claim 8 , further comprising automatically updating the policy in response to a change in a relation between microservices.

10. The method as recited in claim 1 , wherein the restored microservice is restored based in part on required performance of that microservice.

11. 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.

12. The non-transitory storage medium as recited in claim 11 , wherein identifying one or more connections comprises consulting microservice dependency information that was created prior to occurrence of the problem, and the microservice dependency information discloses the one or more connections.

13. The non-transitory storage medium as recited in claim 11 , wherein one of the microservices comprises an element of another application.

14. The non-transitory storage medium as recited in claim 11 , wherein identifying one or more connections among the microservices comprises evaluating a service mesh that includes connection information.

15. The non-transitory storage medium as recited in claim 11 , wherein the restoring is performed according to a policy that was created based on dependency information that discloses the connections among the microservices.

16. The non-transitory storage medium as recited in claim 15 , further comprising automatically updating the policy in response to a change in a relation between microservices.

17. The non-transitory storage medium as recited in claim 11 , wherein the restoration process is performed automatically as a result of receipt of the indication that a problem has occurred.

18. The non-transitory storage medium as recited in claim 11 , wherein the restoring is performed according to a policy that was created based on dependency information that discloses the connections among the microservices.

19. The non-transitory storage medium as recited in claim 18 , further comprising automatically updating the policy in response to a change in a relation between microservices.

20. The non-transitory storage medium as recited in claim 11 , wherein the restored microservice is restored based in part on required performance of that microservice.

Assignees

• Emc Ip Holding Co Llc

Inventors

• Al-Alem Luay
• Bett Antony
• Natanzon Assaf
• Rhodes Michael

Classifications

• G06F2201/82

  Solving problems relating to consistency · CPC title

• G06F11/1438 Primary

  Restarting or rejuvenating · CPC title

• G06F11/1479

  Generic software techniques for error detection or fault masking · CPC title

• G06F2201/805

  Real-time · CPC title