Upon identifying a microservice as a likely source of a process error, system 100 can mark the microservice as faulty. System 100 can select a different version of the microservice (e.g., a prior version that executed by one or more processes without error) and retrieve the different version of the microservice from a networked microservice repository via communications network 102. 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.

One or more databases 108 can include a database, or several databases, that electronically store the software instructions (code) corresponding to various versions of the microservices. System 100 can utilize data (e.g., metadata) retrieved by associator 110 to identify a source of the prior version of a microservice and retrieve the prior version from the source to facilitate the roll back. The data, for example, can provide a microservice ID, version number, date the microservice was deployed, microservice vendor, and the like. System 100 can use the data to identify a database from among the one or more databases 108 from which the software instructions comprising the microservice can be retrieved. The software instructions can be retrieved from the database by system 100 via communications network 102. Alternatively, or additionally, system 100 can itself store prior versions of a microservice. For example, system 100 can store the prior versions as a clear-text matrix.