Abstract: Described are techniques for exposing an endpoint for a software function used by microservices. The techniques include obtaining software classes of a plurality of microservices and analyzing the software classes to identify a software function that is eligible for conversion to an application programming interface (API) format. The techniques further include determining a server microservice, which hosts a software class that includes the software function, and one or more client microservices that use the software function. The techniques further include generating deployable source code implementing an API that exposes the software function hosted by the server microservice to the one or more client microservices. The API uses a software wrapper to encapsulate software function semantics used by a monolith application refactored into the plurality of microservices.

Abstract: One or more application programming interfaces to be implemented for an application are automatically identified. The automatically identifying includes determining within the application one or more artifacts to be implemented as the one or more application programming interfaces. For an artifact of the one or more artifacts, one or more requests of the artifact are determined. The one or more requests are part of an application programming interface signature for an application programming interface identified based on the artifact. For an application programming interface identified based on the artifact, one or more definitions are generated. The one or more definitions include one or more definitions for the one or more requests of the artifact.

Abstract: Described are techniques for exposing an endpoint for a software function used by microservices. The techniques include obtaining software classes of a plurality of microservices and analyzing the software classes to identify a software function that is eligible for conversion to an application programming interface (API) format. The techniques further include determining a server microservice, which hosts a software class that includes the software function, and one or more client microservices that use the software function. The techniques further include generating deployable source code implementing an API that exposes the software function hosted by the server microservice to the one or more client microservices. The API uses a software wrapper to encapsulate software function semantics used by a monolith application refactored into the plurality of microservices.

Abstract: A computer-implemented method includes receiving, by a processor, real time operation data related to an application, identifying components of the application based on the operation data, extracting relationships and interdependencies between the components, and generating a graph of the identified components, the relationships and the interdependencies. The method also includes determining one or more dynamic metrics of the identified components, the one or more dynamic metrics indicative of interactions between the components, extracting statistical information describing at least one of performance and resource consumption based on the operation data, incorporating the dynamic metrics into the graph, determining a behavior of at least one component based on a pattern of appearance of the at least one component in the graph, and generating a model of the application based on the identified components and the determined behaviors.