System, method, and computer program for orchestrating patching of microservices
US-2023351020-A1 · Nov 2, 2023 · US
US12287879B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12287879-B2 |
| Application number | US-202217731142-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 27, 2022 |
| Priority date | Apr 27, 2022 |
| Publication date | Apr 29, 2025 |
| Grant date | Apr 29, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
As described herein, a system, method, and computer program are provided orchestrating patching of microservices. A plurality of microservice patches are detected, the plurality of microservice patches made available for a plurality of different cloud platforms each provided by a different cloud provider of a plurality of cloud providers. Further, installation of the plurality of microservice patches in a running production system is centrally managed.
Opening claim text (preview).
What is claimed is: 1. A non-transitory computer-readable media storing computer instructions which when executed by one or more processors of a device cause the device to: determine a plurality of microservices utilized by a running production system of an organization and defining an application of the organization, wherein the plurality of microservices are provided by a plurality of different cloud providers and wherein each microservice of the plurality of microservices are executed via: a single preparation container that contains executable application code for the microservice, wherein the single preparation container is usable across a plurality of different cloud platforms of the plurality of different cloud providers, a generic infrastructure container that is separate from the single preparation container and that includes a guest operating system of a specific cloud platform of the plurality of different cloud platforms, an executable Kubernetes pod that includes the single prep container and the generic infrastructure container and that includes a shared folder to which the executable application code for the microservice is copied from the single prep container for access by the generic infrastructure container to run the microservice wherein the microservice executes on the specific cloud platform of the plurality of different cloud platforms using the executable Kubernetes pod; detect a plurality of microservice patches made available for the plurality of microservices by the plurality of different cloud providers; and centrally manage installation of the plurality of microservice patches for the application, including for each microservice of the plurality of microservices: applying a microservice patch of the plurality of microservice patches to the generic infrastructure container that is being used to run the microservice such that the microservice patch is installed without changing the executable application code for the microservice. 2. The non-transitory computer-readable media of claim 1 , wherein the plurality of microservice patches are updates to the plurality of microservices inutilized by the running production system. 3. The non-transitory computer-readable media of claim 1 , wherein the microservice patches are applied to the plurality of generic infrastructure containers by constructing a plurality of new generic infrastructure containers having the microservice patches. 4. A method, comprising: at a computer system: determining a plurality of microservices utilized by a running production system of an organization and defining an application of the organization, wherein the plurality of microservices are provided by a plurality of different cloud providers and wherein each microservice of the plurality of microservices are executed via: a single preparation container that contains executable application code for the microservice, wherein the single preparation container is usable across a plurality of different cloud platforms of the plurality of different cloud providers, a generic infrastructure container that is separate from the single preparation container and that includes a guest operating system of a specific cloud platform of the plurality of different cloud platforms, an executable Kubernetes pod that includes the single prep container and the generic infrastructure container and that includes a shared folder to which the executable application code for the microservice is copied from the single prep container for access by the generic infrastructure container to run the microservice wherein the microservice executes on the specific cloud platform of the plurality of different cloud platforms using the executable Kubernetes pod; detecting a plurality of microservice patches made available for the plurality of microservices by the plurality of different cloud providers; and centrally managing installation of the plurality of microservice patches for the application, including for each microservice of the plurality of microservices: applying a microservice patch of the plurality of microservice patches to the generic infrastructure container that is being used to run the microservice such that the microservice patch is installed without changing the executable application code for the microservice. 5. A system, comprising: a non-transitory memory storing instructions; and one or more processors in communication with the non-transitory memory that execute the instructions to: determine a plurality of microservices utilized by a running production system of an organization and defining an application of the organization, wherein the plurality of microservices are provided by a plurality of different cloud providers and wherein each microservice of the plurality of microservices are executed via: a single preparation container that contains executable application code for the microservice, wherein the single preparation container is usable across a plurality of different cloud platforms of the plurality of different cloud providers, a generic infrastructure container that is separate from the single preparation container and that includes a guest operating system of a specific cloud platform of the plurality of different cloud platforms, an executable Kubernetes pod that includes the single prep container and the generic infrastructure container and that includes a shared folder to which the executable application code for the microservice is copied from the single prep container for access by the generic infrastructure container to run the microservice wherein the microservice executes on the specific cloud platform of the plurality of different cloud platforms using the executable Kubernetes pod; detect a plurality of microservice patches made available for the plurality of microservices by the plurality of different cloud providers; and centrally manage installation of the plurality of microservice patches for the application, including for each microservice of the plurality of microservices: applying a microservice patch of the plurality of microservice patches to the generic infrastructure container that is being used to run the microservice such that the microservice patch is installed without changing the executable application code for the microservice.
involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title
Updates (security arrangements therefor G06F21/57) · CPC title
Installation · CPC title
Machine learning · CPC title
Isolation or security of virtual machine instances · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.