Microservice management system for recommending modifications to optimize operation of microservice-based systems

Patent metadata

Field	Value
Publication number	US-2021234930-A1
Application number	US-202016752798-A
Country	US
Kind code	A1
Filing date	Jan 27, 2020
Priority date	Jan 27, 2020
Publication date	Jul 29, 2021
Grant date	—

Abstract

A method, system and computer-usable medium are disclosed for executing a comparative analysis of microservice profiles and recommending modifications to a microservice. In at least one embodiment, a plurality of microservice analysis daemons and a plurality of microservices are deployed to nodes of a network. Run-time execution characteristic of the plurality of microservices are monitored and gathered by the analysis daemons for microservices executed at the node at which the microservice analysis daemon is deployed. Microservice profiles are generated using the run-time execution characteristics data and data retrieved from a service registry. Recommendations regarding modification of one or more microservices are made based on the results of a microservice profile comparative analysis.

First claim

What is claimed is:

1 . A computer-implemented method for managing microservices, comprising:
executing a plurality of microservice analysis daemons on nodes of a network; deploying a plurality of microservices to the nodes of the network; registering the plurality of microservices executed at the nodes of the network with a service registry; gathering execution characteristic data for the plurality of microservices using the microservice analysis daemons, wherein the microservice analysis daemons gather execution characteristic data for microservices executed at the node at which the microservice analysis daemon is deployed; generating microservice profiles for the plurality of microservices using execution characteristics data obtained from the microservice analysis daemons and data retrieved from the service registry; executing a comparison operation using the microservice profiles; and making recommendations regarding modification of one or more microservices based on results of the comparison operation.

2 . The computer-implemented method of claim 1 , wherein
the microservice profiles are further generated using microservice information retrieved from a datastore, wherein the microservice information includes information for the microservices provided by microservice owners.

3 . The computer-implemented method of claim 2 , wherein
the microservice information further includes information derived from a lexical analysis of a microservice codebase, wherein the microservice codebase includes code for the plurality of microservices.

4 . The computer-implemented method of claim 1 , wherein
the microservice profiles include records respectively associated with the microservice profiles, wherein the record for a profile includes tokenized information including one or more of:
keywords associated with code characteristics of the microservice;
variables and/or function names used by the microservice;
literals used by the microservice; and
text comments associated with the microservice.

5 . The computer-implemented method of claim 1 , further comprising:
making a recommendation to eliminate a microservice and use another microservice when
the microservice receives the same payload type as the other microservice; and
the microservice outputs the same payload type as the other microservice.

6 . The computer-implemented method of claim 1 , further comprising:
making a recommendation to consolidate functionality of a microservice with another microservice when the microservice consistently communicates with the same microservices as the other microservice and has at least some overlapping functionality.

7 . The computer-implemented method of claim 1 , further comprising:
making a recommendation to update a microservice to maintain a consistent payload format with other similar microservices.

8 . A system comprising:
a processor; a data bus coupled to the processor; and a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for:
executing a plurality of microservice analysis daemons on nodes of a network;
deploying a plurality of microservices to the nodes of the network;
registering the plurality of microservices executed at the nodes of the network with a service registry;
gathering execution characteristic data for the plurality of microservices using the microservice analysis daemons, wherein the microservice analysis daemons gather execution characteristic data for microservices executed at the node at which the microservice analysis daemon is deployed;
generating microservice profiles for the plurality of microservices using execution characteristics data obtained from the microservice analysis daemons and data retrieved from the service registry;
executing a comparison operation using the microservice profiles; and
making recommendations regarding modification of one or more microservices based on results of the comparison operation.

9 . The system of claim 8 , wherein
the microservice profiles are further generated using microservice information retrieved from a datastore, wherein the microservice information includes information for the microservices provided by microservice owners.

10 . The system of claim 9 , wherein
the microservice information further includes information derived from a lexical analysis of a microservice codebase, wherein the microservice codebase includes code for the plurality of microservices.

11 . The system of claim 8 , wherein
the microservice profiles include records respectively associated with the microservice profiles, wherein the record for a profile includes tokenized information including one or more of:
keywords associated with code characteristics of the microservice;
variables and/or function names used by the microservice;
literals used by the microservice; and
text comments associated with the microservice.

12 . The system of claim 8 , wherein the instructions are further configured for:
making a recommendation to eliminate a microservice and use another microservice when the microservice receives the same payload type as the other microservice; and the microservice outputs the same payload type as the other microservice.

13 . The system of claim 8 , wherein the instructions are further configured for:
making a recommendation to consolidate functionality of a microservice with another microservice when the microservice consistently communicates with the same microservices as the other microservice and has at least some overlapping functionality.

14 . The system of claim 8 , wherein the instructions are further configured for:
making a recommendation to update a microservice to maintain a consistent payload format with other similar microservices.

15 . A non-transitory, computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for:
executing a plurality of microservice analysis daemons on nodes of a network; deploying a plurality of microservices to the nodes of the network; registering the plurality of microservices executed at the nodes of the network with a service registry; gathering execution characteristic data for the plurality of microservices using the microservice analysis daemons, wherein the microservice analysis daemons gather execution characteristic data for microservices executed at the node at which the microservice analysis daemon is deployed; generating microservice profiles for the plurality of microservices using execution characteristics data obtained from the microservice analysis daemons and data retrieved from the service registry; executing a comparison operation using the microservice profiles; and making recommendations regarding modification of one or more microservices based on results of the comparison operation.

16 . The non-transitory, computer-readable storage medium of claim 15 , wherein
the microservice profiles are further generated using microservice information retrieved from a datastore, wherein the microservice information includes information for the microservices provided by microservice owners.

17 . The non-transitory, computer-readable storage medium of claim 16 , wherein
the microservice information further includes information der

Assignees

• Dell Products Lp

Inventors

• Dinh Hung The
• Gupta Shubham

Classifications

• H04L67/63

  Routing a service request depending on the request content or context · CPC title

• H04L67/51 Primary

  Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

• G06F9/44505

  Configuring for program initiating, e.g. using registry, configuration files · CPC title

• G06F8/60

  Software deployment · CPC title

• G06F9/453

  Help systems · CPC title