Automatically determining and modifying environments for running microservices in a performant and cost-effective manner

A computer implemented method for configuring each one of a plurality of microservices to generate runtime metering data concerning at least their invocations, and subsequently automatically managing deployments of the plurality of microservices executing in a cloud, the method comprising:

• prior to deployment of each one of the microservices of the plurality, configuring each one of the microservices of the plurality to generate runtime metering data concerning at least their invocations;
• monitoring rates of invocation of each one of the plurality of microservices over a plurality of given periods of time by monitoring the metering data generated by each one of by the plurality of microservices;
• and
• responsive to a given monitored rate of invocation of a specific one of the plurality of microservices executing on a first deployment configuration exceeding a predetermined threshold, automatically redeploying the specific microservice to a second deployment configuration;
• wherein the first deployment configuration and the second deployment configuration are different;
• wherein the first deployment configuration further comprises a serverless deployment in the cloud;
• and
• wherein the second deployment configuration further comprises a dedicated node configured to execute the specific one of the plurality of microservices in the cloud.

At least one non-transitory computer-readable storage medium for configuring a microservice prior to deployment, and subsequently automatically modifying a deployment configuration of the microservice executing in a cloud, the at least one non-transitory computer-readable storage medium storing computer executable instructions that, when loaded into computer memory and executed by at least one processor of a computing device, cause the computing device to perform the following steps:

• prior to deployment of the microservice, configuring the microservice to generate runtime metering data concerning at least its invocations;
• monitoring a rate of invocation of the microservice executing on a first deployment configuration over a given period of time by monitoring the metering data generated by the microservice;
• and
• responsive to the monitored rate of invocation exceeding a predetermined threshold, automatically redeploying the microservice to a second deployment configuration;
• wherein the first deployment configuration and the second deployment configuration are different;
• wherein the first deployment configuration further comprises a serverless deployment in the cloud;
• and
• wherein the second deployment configuration further comprises a dedicated node configured to execute the microservice in the cloud.