Microservice update system

Patent metadata

Field	Value
Publication number	US-11093232-B2
Application number	US-201916503146-A
Country	US
Kind code	B2
Filing date	Jul 3, 2019
Priority date	Apr 30, 2019
Publication date	Aug 17, 2021
Grant date	Aug 17, 2021

Abstract

A microservice update system includes a build dispatcher system that receives a microservice modification request identifying first microservice(s) included in a plurality of microservices that provide a service. The build dispatcher system then triggers a respective microservice pipeline for each first microservice. A continuous integration system receives respective microservice modified code for each first microservice via the respective pipeline triggered for each, and update corresponding first portion(s) of service code. The continuous integration system then tests the updated service code in order to test the first microservice(s) that are provided by the first portion(s) of updated service code, and test second microservice(s) that are included in the plurality of microservices that provide the service, that are provided by at least one second portion of the updated service code that was not updated as part of the updating, and that are dependent on at least one of the first microservice(s).

First claim

What is claimed is:

1. A microservice update system, comprising:
a build dispatcher system that includes:
a first non-transitory memory; and
a first processor that is coupled to the first non-transitory memory and that is configured to read instructions from the first non-transitory memory to cause the builder dispatcher system to be configured to:
receive a microservice modification request;
identify a first subset of microservices that are included in a plurality of microservices that are configured to provide a service, and for which a modification has been requested in the microservice modification request; and
trigger, for each of the first subset of microservices, a respective microservice pipeline that is associated with a respective root of a respective microservice folder for each of the first subset of microservices; and

a continuous integration system that is coupled to the build dispatcher system and that includes:
a second non-transitory memory; and
a second processor that is coupled to the first non-transitory memory and that is configured to read instructions from the first non-transitory memory to cause the continuous integration system to be configured to:
receive, via the respective pipeline triggered for each of the first subset of microservices, respective microservice modified code for each of the first subset of microservices;
update, using the respective microservice modified code for each of the first subset of microservices, at least one first portion of service code that provides the first subset of microservices for the service, wherein the updating provides updated service code; and
test the updated service code in order to test:
the first subset of microservices that are provided by the at least one first portion of the updated service code; and
a second subset of microservices that are included in the plurality of microservices that are configured to provide the service, that are provided by at least one second portion of the updated service code that was not updated as part of the updating, and that are dependent on at least one of the first subset of microservices.

2. The system of claim 1 , wherein the continuous integration system is configured to:
determine, in response to the testing of the updated service code, that each of the first subset of microservices and the second subset of microservice have passed the testing; and
provide, for display on a developer system, an indication that each of the first subset of microservices and the second subset of microservice have passed the testing.

3. The system of claim 1 , wherein the continuous integration system is configured to:
automatically deploy, to a service provisioning system in response to determining that each of the first subset of microservices and the second subset of microservices have passed the testing, the updated service code.

4. The system of claim 1 , wherein the continuous integration system is configured to:
determine, in response to the testing of the updated service code, that at least one of the first subset of microservices and the second subset of microservices have not passed the testing; and
provide, for display on a developer system, an indication that at least one of the first subset of microservices and the second subset of microservices have not passed the testing.

5. The system of claim 1 , wherein the second subset of microservices are dependent on the at least one subset of microservices based on the second subset of microservices utilizing at least one output generated by the at least one subset of microservices during the testing.

6. The system of claim 1 , wherein the first subset of microservices includes at least two microservices, and wherein the updating of the at least one first portion of service code that provides the first subset of microservices for the service includes updating the at least two microservices included in the first subset of microservices in parallel.

7. An Information Handling System (IHS), comprising:
a memory system that includes a non-transitory memory; and
a processing system that includes a processor
that is coupled to the memory system and that is configured to read instructions from the non-transitory memory to cause the processing system to provide a continuous integration engine that is configured to:
receive, for each of a first subset of microservices that are included in a plurality of microservices that are configured to provide a service and for which a modification has been requested and via a respective pipeline triggered for each of the first subset of microservices, respective microservice modified code for each of the first subset of microservices, wherein each respective pipeline is associated with a respective root of a respective microservice folder for each of the first subset of microservices;
update, using the respective microservice modified code for each of the first subset of microservices, at least one first portion of service code that provides the first subset of microservices for the service, wherein the updating provides updated service code; and
test the updated service code in order to test:
the first subset of microservices that are provided by the at least one first portion of the updated service code; and
a second subset of microservices that are included in the plurality of microservices that are configured to provide the service, that are provided by at least one second portion of the updated service code that was not updated as part of the updating, and that are dependent on at least one of the first subset of microservices.

8. The IHS of claim 7 , wherein the continuous integration engine is configured to:
determine, in response to the testing of the updated service code, that each of the first subset of microservices and the second subset of microservice have passed the testing; and
provide, for display on a developer system, an indication that each of the first subset of microservices and the second subset of microservice have passed the testing.

9. The IHS of claim 8 , wherein the continuous integration engine is configured to:
automatically deploy, to a service provisioning system in response to determining that each of the first subset of microservices and the second subset of microservices have passed the testing, the updated service code.

10. The IHS of claim 7 , wherein the continuous integration engine is configured to:
determine, in response to the testing of the updated service code, that at least one of the first subset of microservices and the second subset of microservices have not passed the testing; and
provide, for display on a developer system, an indication that at least one of the first subset of microservices and the second subset of microservices have not passed the testing.

11. The IHS of claim 7 , wherein the second subset of microservices are dependent on the at least one subset of microservices based on the second subset of microservices utilizing at least one output generated by the at least one subset of microservices during the testing.

12. The IHS of claim 7 , wherein the first subset of microservices includes at least two microservices, and wherein the updating of the at least one first portion of service code that provides the first subset of microservices for the service includes updating the at least two microservices included in the first subset of microservices in parallel.

13. The IHS of claim 7 , wherein the processor is configured to read instructions from the non-transitory memory system to cause the processing system to provide a build dispatcher engine that is configured to:
receive a m

Assignees

• Dell Products Lp

Inventors

• Maréchal Marc Marcel René
• Shi Yongjun

Classifications

• G06F11/3688

  for test execution, e.g. scheduling of test suites · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title

• G06F8/71

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F11/3672

  Test management · CPC title