Prioritizing microservices on a container platform for a restore operation

Patent metadata

Field	Value
Publication number	US-10853196-B2
Application number	US-201816053976-A
Country	US
Kind code	B2
Filing date	Aug 3, 2018
Priority date	Aug 3, 2018
Publication date	Dec 1, 2020
Grant date	Dec 1, 2020

Abstract

Systems and methods for discovering applications. An application may be discovered by determining a topology of the application in a containerized platform. Discovering the topology may include determining the components of the application and then determining relationships between the components. The relationships may include whether a component (e.g., a microservice) is user facing and may be based on traffic patterns between the components. The components or microservices may be prioritized or ranked based on the topology. The topology can be used when performing a data protection operation such as a restore operation.

First claim

What is claimed is:

1. A method, comprising:
performing a first query to a container platform to determine microservices of an application operating in the container platform;
performing a second query to a mesh platform to determine relationships between the microservices of the application, the relationships including traffic patterns to and from the microservices of the application;
determining a topology of the application based on results of the first query and the second query; and
prioritizing the microservices based on the topology and the results for a restore operation.

2. The method of claim 1 , further comprising prioritizing the microservices into a plurality of tiers.

3. The method of claim 2 , wherein the plurality of tiers include a first tier, a second tier, and a third tier, wherein the first tier corresponds to microservices that are most important for data protection.

4. The method of claim 2 , further comprising determining which microservices are user-facing microservices, wherein the user-facing microservices are placed in a first tier of the plurality of tiers.

5. The method of claim 2 , wherein microservices that are not user facing are placed in the second tier or the third tier.

6. The method of claim 1 , the relationships further including the traffic patterns between interconnected microservices.

7. The method of claim 6 , wherein microservices having traffic patterns that are higher than traffic patterns of other microservices have a higher prioritization.

8. The method of claim 1 , further comprising restoring the microservices based on their prioritizations.

9. The method of claim 8 , further comprising identifying user-facing microservices, internal microservices, and low level microservices based on the results.

10. The method of claim 9 , wherein the user: facing microservices are restored before the internal microservices and before the low level microservices.

11. A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
performing a first query to a container platform to determine microservices of an application operating in the container platform;
performing a second query to a mesh platform to determine relationships between the microservices of the application, the relationships including traffic patterns to and from the microservices of the application;
determining a topology of the application based on results of the first query and the second query; and
prioritizing the microservices based on the topology and the results for a restore operation.

12. The non-transitory storage medium of claim 11 , further comprising prioritizing the microservices into a plurality of tiers.

13. The non-transitory storage medium of claim 12 , wherein the plurality of tiers include a first tier, a second tier, and a third tier, wherein the first tier corresponds to microservices that are most important for data protection.

14. The non-transitory storage medium of claim 12 , further comprising determining which microservices are user-facing microservices, wherein the user-facing microservices are placed in a first tier of the plurality of tiers.

15. The non-transitory storage medium of claim 12 , wherein microservices that are not user facing are placed in the second tier or the third tier.

16. The non-transitory storage medium of claim 11 , the relationships further including the traffic patterns between interconnected microservices.

17. The non-transitory storage medium of claim 16 , wherein microservices having traffic patterns that are higher than traffic patterns of other microservices have a higher prioritization.

18. The non-transitory storage medium of claim 11 , further comprising restoring the microservices based on their prioritizations.

19. The non-transitory storage medium of claim 18 , further comprising identifying user-facing microservices, internal microservices, and low level microservices based on the results.

20. The non-transitory storage medium of claim 19 , wherein the user-facing microservices are restored before the internal microservices and before the low level microservices.

Assignees

• Emc Ip Holding Co Llc

Inventors

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

Classifications

• G06F16/27 Primary

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

• G06F11/1469 Primary

  Backup restoration techniques · CPC title

• G06F2201/84

  Using snapshots, i.e. a logical point-in-time copy of the data · CPC title

• G06F16/245

  Query processing · CPC title

• G06F8/65

  Updates (security arrangements therefor G06F21/57) · CPC title