Prioritizing microservices on a container platform for a restore operation
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.
1. A method, comprising:
identifying microservices of an application, wherein the application operates in a container platform, wherein the container platform includes a mesh platform that connects and manages the microservices;
identifying relationships between the microservices of the application, wherein the relationships include traffic patterns between the microservices observed by the mesh platform;
determining a topology of the application based on the identified microservices and the identified relationships;
prioritizing the microservices based on the topology and the relationships; and
performing a restore operation to restore the microservices based on the prioritizations of the microservices.
2. The method of claim 1 , further comprising prioritizing the microservices based on factors including one or more of whether a microservice is a user or non-user facing microservice, a workload microservice, or a metadata microservice.
3. The method of claim 1 , further comprising updating the topology and the prioritizations.
4. The method of claim 1 , wherein prioritizing the microservices includes ranking the microservices.
5. The method of claim 1 , wherein identifying the microservices includes querying the container platform to extract details of a microservice including one or more of container image, container metadata, environment variables, attached storage, remote services, platform configuration, ingress traffic, and egress traffic.
6. The method of claim 1 , wherein identifying the relationships includes querying the mesh network to identify routes of all traffic to and from the microservices using listeners attached to the microservices.
7. The method of claim 1 , further comprising prioritizing the microservices based on hits to the microservices.
8. The method of claim 1 , further comprising ranking the microservices into a plurality of tiers.
9. The method of claim 8 , wherein microservices in higher ranked tiers are restored before microservices in lower ranked tiers.
10. The method of claim 1 , wherein the application includes containers, back end services, and Application Programming Interfaces (APIs).
11. A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
identifying microservices of an application, wherein the application operates in a container platform, wherein the container platform includes a mesh platform that connects and manages the microservices;
identifying relationships between the microservices of the application, wherein the relationships include traffic patterns between the microservices observed by the mesh platform;
determining a topology of the application based on the identified microservices and the identified relationships;
prioritizing the microservices based on the topology and the relationships; and
performing a restore operation to restore the microservices based on the prioritizations of the microservices.
12. The non-transitory storage medium of claim 11 , further comprising prioritizing the microservices based on factors including one or more of whether a microservice is a user or non-user facing microservice, a workload microservice, or a metadata microservice.
13. The non-transitory storage medium of claim 11 , further comprising updating the topology and the prioritizations.
14. The non-transitory storage medium of claim 11 , wherein prioritizing the microservices includes ranking the microservices.
15. The non-transitory storage medium of claim 11 , wherein identifying the microservices includes querying the container platform to extract details of a microservice including one or more of container image, container metadata, environment variables, attached storage, remote services, platform configuration, ingress traffic, and egress traffic.
16. The non-transitory storage medium of claim 11 , wherein identifying the relationships includes querying the mesh network to identify routes of all traffic to and from the microservices using listeners attached to the microservices.
17. The non-transitory storage medium of claim 11 , further comprising prioritizing the microservices based on hits to the microservices.
18. The non-transitory storage medium of claim 11 , further comprising ranking the microservices into a plurality of tiers.
19. The non-transitory storage medium of claim 18 , wherein microservices in higher ranked tiers are restored before microservices in lower ranked tiers.
20. The non-transitory storage medium of claim 11 , wherein the application includes containers, back end services, and Application Programming Interfaces (APIs).