Based on the comparisons, analyzer 114 can generate analytics to assess the likely effects of changes in or modifications to a network of microservices and/or individual processes that use one or more of the microservices. For example, analyzer 114 can perform a matrix subtraction to subtract a proposed microservices network structure from a current version, which can identify for a DevOps team the specific microservices and/or interfaces between microservice pairs that are most likely to affect the network's or an individual process's performance or dynamic behavior. Analyzer 114 can use the same procedure if a process, newly updated by a change in or modification to one or more microservices, fails to perform properly. Analyzer 114 can identify for the DevOps team the microservice that most likely needs to be rolled back in order to bring the process back to a “normal” or “well-functioning” state. Algorithmic aspects of the procedures for assessing the effects of changes to microservices are described in the context of the following examples. Although described for ease of presentation and without loss of generality in the context of asynchronous process instances (e.g., messages), it is noted that the procedures are equally applicable with respect synchronous process instances (e.g., RESTful-APIs).