FIG. 4 is a flowchart of method 400 for managing microservice changes and performing related analytics according to one embodiment. Method 400 can be performed by a system the same or similar to the systems described with reference to FIGS. 1-3. The system at block 402 generates multiple process instance representations. 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 the microservices.

The system at block 404 constructs a microservices network representation based on the process instance representations. Each element of the microservices network corresponds to an interface between a pair of the microservices. At block 406, the system determines a relative frequency for each of the microservices based on the microservices network representation. Each relative frequency corresponds to a likelihood that a change in a microservice will affect a performance or the functioning of at least one process using at least one of the microservices.

The process instance representations, in certain embodiments, comprise invocation matrices. In certain embodiments, the microservices network representation comprises a network matrix constructed by performing a matrix addition that sums multiple invocation matrices. The system in certain embodiments determines the relative frequencies of each of the microservices by generating a relative frequency matrix based on the network matrix.

A change in a microservice can be a change in an interface between the microservice and another process using at least one of the microservices. The change can be a substitution of one version of the microservice for another version of the microservice.