IP Library › Granted Patent US 10,241,778

Granted Patent B2

US 10,241,778 · App. 15/277,269 · Granted Mar 26, 2019

Microservices version state visualization

Inventors: Mark W. Emeis (Monument, CO); Robert C. Hendrich (Colorado Springs, CO); Dann M. Church (Castle Rock, CO); Craig Andrew Vosburgh (Colorado Springs, CO)

Assignee: CA, Inc.

G06F8/65 G06F8/71 G06F9/451 G06T11/206

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 10,241,778
App. No.: 15/277,269
Granted: Mar 26, 2019
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

In one embodiment, configuration information for a microservices application is obtained, the microservices application comprising a plurality of microservice containers, and the configuration information comprising version information for each of the plurality of microservice containers. A graphical representation of the microservices application is displayed, wherein the graphical representation of the microservices application comprises a representation of each of the plurality of microservice containers. It is determined, based on the version information, whether each of the plurality of microservice containers is updated or outdated. A graphical indication of an updated microservice container is displayed; a graphical indication of an outdated microservice container is displayed; and a graphical indication of an extent to which the outdated microservice container is out-of-date is displayed.

Claims (94)

1. A method comprising:

identifying a current implementation of a microservices application, wherein the microservices application comprises a plurality of microservice containers, and wherein each microservice container comprises an environment for executing a particular microservice on one or more processors;

determining version state information for the microservices application, wherein the version state information comprises an indication of:

one or more up-to-date microservice containers from the plurality of microservice containers;

one or more out-of-date microservice containers from the plurality of microservice containers; and

an extent to which the one or more out-of-date microservice containers are outdated;

displaying a graphical representation of the microservices application, wherein the graphical representation of the microservices application comprises:

a graphical representation of the plurality of microservice containers; and

a plurality of version state visualizations, wherein the plurality of version state visualizations comprises a plurality of graphical indications of: the one or more up-to-date microservice containers; the one or more out-of-date microservice containers; and the extent to which the one or more out-of-date microservice containers are outdated;

prompting a user regarding whether to update the one or more out-of-date microservice containers; and

updating the one or more out-of-date microservice containers based on prompting the user.

2. The method of claim 1 , wherein determining the version state information for the microservices application further comprises:

determining that an update is available for a particular out-of-date microservice container of the one or more out-of-date microservice containers; and

determining a backwards compatibility of the update for the particular out-of-date microservice container; and

wherein the plurality of version state visualizations further comprises a graphical indication of the backwards compatibility of the update for the particular out-of-date microservice container.

3. The method of claim 1 , wherein determining the version state information for the microservices application further comprises determining that a bug fix update is available for a particular out-of-date microservice container of the one or more out-of-date microservice containers; and

wherein the plurality of version state visualizations further comprises a graphical indication that the bug fix update is available for the particular out-of-date microservice container.

4. The method of claim 1 :

wherein determining the version state information for the microservices application further comprises determining a risk associated with updating a particular out-of-date microservice container of the one or more out-of-date microservice containers; and

wherein the plurality of version state visualizations further comprises a graphical indication of the risk associated with updating the particular out-of-date microservice container.

5. The method of claim 1 , wherein determining the version state information for the microservices application further comprises:

identifying a current version number for a particular out-of-date microservice container of the one or more out-of-date microservice containers, wherein the particular out-of-date microservice container is used in the current implementation of the microservices application;

identifying an updated version number for an update to the particular out-of-date microservice container; and

determining, based on the current version number and the updated version number, whether the update to the particular out-of-date microservice container comprises a major update, a minor update, or a patch update; and

wherein the plurality of version state visualizations further comprises a graphical indication of whether the update to the particular out-of-date microservice container comprises the major update, the minor update, or the patch update.

6. The method of claim 1 , wherein the plurality of version state visualizations further comprises a plurality of colors indicating the extent to which the one or more out-of-date microservice containers are outdated.

7. The method of claim 6 , wherein the plurality of colors comprises a first color to indicate that a major update is available, a second color to indicate that a minor update is available, and a third color to indicate that a patch is available.

8. The method of claim 1 , wherein determining the version state information for the microservices application further comprises:

identifying a first version of a particular microservice container of the plurality of microservice containers, wherein the first version of the particular microservice container is used in the current implementation of the microservices application;

identifying a second version of the particular microservice container, wherein the second version of the particular microservice container comprises a latest release of the particular microservice container;

determining whether the first version and the second version are different;

determining that the particular microservice container is up-to-date upon a determination that the first version and the second version are not different; and

determining that the particular microservice container is out-to-date upon a determination that the first version and the second version are different.

9. The method of claim 8 , wherein determining whether the first version and the second version are different further comprises:

obtaining a first checksum for the first version of the particular microservice container;

obtaining a second checksum for the second version of the particular microservice container; and

determining whether the first checksum and the second checksum are different.

10. The method of claim 1 , wherein the plurality of version state visualizations further comprises one or more emoticons indicating:

the one or more up-to-date microservice containers;

the one or more out-of-date microservice containers; or

the extent to which the one or more out-of-date microservice containers are outdated.

11. The method of claim 1 , wherein the graphical representation of the microservices application further comprises a graphical representation of one or more relationships between the plurality of microservice containers.

12. A system comprising:

a processor device;

a memory element; and

an application manager stored in the memory element, the application manager comprising one or more instructions executable by the processor device, the one or more instructions configured to:

identify a current implementation of a microservices application, wherein the microservices application comprises a plurality of microservice containers, and wherein each microservice container comprises an environment for executing a particular microservice on the processor device;

determine version state information for the microservices application, wherein the version state information comprises an indication of:

one or more up-to-date microservice containers from the plurality of microservice containers;

one or more out-of-date microservice containers from the plurality of microservice containers; and

an extent to which the one or more out-of-date microservice containers are outdated;

display a graphical representation of the microservices application, wherein the graphical representation of the microservices application comprises:

a graphical representation of the plurality of microservice containers; and

prompt a user regarding whether to update the one or more out-of-date microservice containers; and

update the one or more out-of-date microservice containers based on prompting the user.

13. The system of claim 12 :

wherein the one or more instructions configured to determine the version state information for the microservices application are further configured to determine that a bug fix update is available for a particular out-of-date microservice container of the one or more out-of-date microservice containers; and

wherein the plurality of version state visualizations further comprises a graphical indication that the bug fix update is available for the particular out-of-date microservice container.

14. The system of claim 12 :

wherein the one or more instructions configured to determine the version state information for the microservices application are further configured to determine a risk associated with updating a particular out-of-date microservice container of the one or more out-of-date microservice containers; and

wherein the plurality of version state visualizations further comprises a graphical indication of the risk associated with updating the particular out-of-date microservice container.

15. The system of claim 12 :

wherein the one or more instructions configured to determine the version state information for the microservices application are further configured to:

identify a current version number for a particular out-of-date microservice container of the one or more out-of-date microservice containers, wherein the particular out-of-date microservice container is used in the current implementation of the microservices application;

identify an updated version number for an update to the particular out-of-date microservice container; and

determine, based on the current version number and the updated version number, whether the update to the particular out-of-date microservice container comprises a major update, a minor update, or a patch update; and

16. The system of claim 12 , wherein the plurality of version state visualizations further comprises a plurality of colors indicating the extent to which the one or more out-of-date microservice containers are outdated.

17. The system of claim 12 , wherein the one or more instructions configured to determine the version state information for the microservices application are further configured to:

identify a first version of a particular microservice container of the plurality of microservice containers, wherein the first version of the particular microservice container is used in the current implementation of the microservices application;

identify a second version of the particular microservice container, wherein the second version of the particular microservice container comprises a latest release of the particular microservice container;

determine whether the first version and the second version are different;

determine that the particular microservice container is up-to-date upon a determination that the first version and the second version are not different; and

determine that the particular microservice container is out-to-date upon a determination that the first version and the second version are different.

18. The system of claim 17 , wherein the one or more instructions configured to determine whether the first version and the second version are different are further configured to:

obtain a first checksum for the first version of the particular microservice container;

obtain a second checksum for the second version of the particular microservice container; and

determine whether the first checksum and the second checksum are different.

19. The system of claim 12 , wherein the plurality of version state visualizations further comprises one or more emoticons indicating:

the one or more up-to-date microservice containers;

the one or more out-of-date microservice containers; or

the extent to which the one or more out-of-date microservice containers are outdated.

20. A non-transitory computer readable medium having program instructions stored thereon that are executable to cause a computer system to perform operations comprising: