Microservices Change Management and Analytics

1. A method, comprising: generating, with computer hardware, a plurality of process instance representations, wherein each process instance representation is generated based on a corresponding process path comprising an ordered sequence of operations performed by a process using at least one of a plurality of microservices; constructing a microservices network representation based on the plurality of process instance representations, wherein each element of the microservices network corresponds to an interface between a pair of microservices; and determining based on the microservices network representation a relative frequency for each of the plurality of microservices, each relative frequency corresponding to a likelihood that a change in a microservice will affect performance of at least one process using at least one of the plurality of microservices.

2. The method of claim 1 , wherein the process instance representations comprise invocation matrices and the microservices network representation comprises a network matrix constructed by performing a matrix addition for summing the invocation matrices.

3. The method of claim 2 , wherein the determining comprises generating a relative frequency matrix based on the network matrix.

4. The method of claim 1 , wherein the change in the microservice comprises a change in an interface between the microservice and another process using at least one of the plurality of microservices.

5. The method of claim 1 , wherein the change in the microservice comprises substituting one version of the microservice for another version of the microservice.

6. The method of claim 1 , further comprising responding to a process error by identifying a microservice as a likely source of the process error.

7. The method of claim 6 , further comprising rolling back a current version of the microservice identified as the likely source by marking the microservice as faulty; selecting a different version of the microservice; and retrieving the different version of the microservice from a networked microservice repository.

8. A system, comprising: a processor configured to initiate operations including: generating a plurality of process instance representations, wherein each process instance representation is generated based on a corresponding process path comprising an ordered sequence of operations performed by a process using at least one of a plurality of microservices; constructing a microservices network representation based on the plurality of process instance representations, wherein each element of the microservices network corresponds to an interface between a pair of microservices; and determining based on the microservices network representation a relative frequency for each of the plurality of microservices, each relative frequency corresponding to a likelihood that a change in a microservice will affect performance of at least one process using at least one of the plurality of microservices.

9. The system of claim 8 , wherein the process instance representations comprise invocation matrices and the microservices network representation comprises a network matrix constructed by performing a matrix addition for summing the invocation matrices.

10. The system of claim 9 , wherein the determining comprises generating a relative frequency matrix based on the network matrix.

11. The system of claim 8 , wherein the change in the microservice comprises a change in an interface between the microservice and another process using at least one of the plurality of microservices.

12. The system of claim 8 , wherein the change in the microservice comprises substituting one version of the microservice for another version of the microservice.

13. The system of claim 8 , wherein the processor is configured to initiate operations further comprising: responding to a process error by identifying a microservice as a likely source of the process error; and rolling back a current version of the microservice identified as the likely source by marking the microservice as faulty, selecting a different version of the microservice, and retrieving the different version of the microservice from a networked microservice repository.

14. A computer program product, the computer program product comprising: one or more computer-readable storage media and program instructions collectively stored on the one or more computer-readable storage media, the program instructions executable by a processor to cause the processor to initiate operations including: generating, with computer hardware, a plurality of process instance representations, wherein each process instance representation is generated based on a corresponding process path comprising an ordered sequence of operations performed by a process using at least one of a plurality of microservices; constructing a microservices network representation based on the plurality of process instance representations, wherein each element of the microservices network corresponds to an interface between a pair of microservices; and determining based on the microservices network representation a relative frequency for each of the plurality of microservices, each relative frequency corresponding to a likelihood that a change in a microservice will affect performance of at least one process using at least one of the plurality of microservices.

15. The computer program product of claim 14 , wherein the process instance representations comprise invocation matrices and the microservices network representation comprises a network matrix constructed by performing a matrix addition for summing the invocation matrices.

16. The computer program product of claim 15 , wherein the determining comprises generating a relative frequency matrix based on the network matrix.

17. The computer program product of claim 14 , wherein the change in the microservice comprises a change in an interface between the microservice and another process using at least one of the plurality of microservices.

18. The computer program product of claim 14 , wherein the change in the microservice comprises substituting one version of the microservice for another version of the microservice.

19. The computer program product of claim 14 , further comprising responding to a process error by identifying a microservice as a likely source of the process error.

20. The computer program product of claim 19 , further comprising rolling back a current version of the microservice identified as the likely source by marking the microservice as faulty; selecting a different version of the microservice; and retrieving the different version of the microservice from a networked microservice repository.