In one or more embodiments, method 400 further comprises the system responding to a process error by identifying a microservice as a likely source of the process error. Referring additionally to FIG. 5, a flowchart of method 500 responding to a process error according to an embodiment is depicted. Method 500 also can be performed by a system the same or similar to the systems described in reference to FIGS. 1-3. The system at block 502 identifies the microservice that is the likely source of a process error. At block 504, the system marks the microservice identified as the likely source of the process error as faulty. At block 506, the system selects a different version of the microservice and, at block 508, retrieves the different version of the microservice from a networked microservice repository. If the system determines that in fact the microservice is the source of the process error, then the process invokes the substitute version of the microservice when the process executes on a computer system. In the event that more than one microservice is determined to be possibly faulty, the system can apply the procedure iteratively beginning with the microservice having the highest relative frequency of invocation and continue until the microservice or microservices that are in fact faulty are discovered and rolled back.

It is expressly noted that although this disclosure includes a detailed description on cloud computing, implementations of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.