Constructor 112 constructs different representations of different classes of data corresponding to individual processes and the constituent microservices from which the processes are built. In certain embodiments described in greater detail below, constructor 112, using interface data retrieved by associator 110, generates an n-element vector, or n-tuple, that represents a process as a process path. A process path, as constructed by constructor 112, is an ordered sequence of the microservices, the ordered sequence specifying the order in which each microservice is invoked in performing the operations carried out by executing the process on a computer system. Accordingly, in a vector representation, each element of the vector can correspond to a microservice ID, and the element's position within the vector can indicate the order in which the microservice is invoked during execution of the process.

For example, the vector (x₁, x₂, . . . , x₈)=(start, 1, 3, 1, 2, 5, 6, end) illustrates the representation of an asynchronous function (e.g., message) built from six microservices, numbered 1 through 6, that operate in the indicated sequence—specifically, execution of the process starts with the microservice whose ID is one. After microservice one executes, the microservice whose ID is invoked, after which microservice one again executes, followed by the microservice whose ID is two, and so on, until the microservice whose ID is six executes thereby ending execution of the process represented by process path vector (start, 1, 3, 1, 2, 5, 6, end).