IP Library Granted Patent US 12,481,543
Granted Patent B2
US 12,481,543 · App. 17/989,731 · Granted Nov 25, 2025

Cloud-distributed application runtime—an emerging layer of multi-cloud application services fabric

Inventors: Emad Benjamin (San Jose, CA); Pere Monclus (Santa Clara, CA); Diwan Chandrabose (Bangalore, IN); Abhijit Patharkar (Pune, IN); Abhirama Mallela (Bangalore, IN)
Assignee: VMware LLC
G06F9/547H04L63/1416
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 12,481,543
App. No.
17/989,731
Granted
Nov 25, 2025
Kind
B2
Abstract

A cloud distributed application runtime is deployed to execute a cloud infrastructure. During deployment of an application service by the cloud infrastructure, each action implemented in the cloud infrastructure is traced, from an initiation of the application service to a termination of the application service. Level objectives associated with the cloud infrastructure and associated with the application service deployed by the cloud infrastructure are tracked. In response to tracing an action implemented in the cloud infrastructure and in response to tracking the level objectives, a scaling decision associated with the application service is determined. The scaling decision incudes either an upscaling or a downscaling. In response to determining the scaling decision, the scaling decision is implemented to match the level objectives associated with the cloud infrastructure and associated with the application service.

Claims (74)

1 . A computer-implemented method to deploy a runtime to execute a cloud infrastructure, the method comprising:

tracing each action implemented in the cloud infrastructure during deployment, by the cloud infrastructure of an application service, from an initiation of the application service to a termination of the application service;

tracking level objectives associated with the cloud infrastructure and associated with the application service deployed by the cloud infrastructure;

in response to tracing an action implemented in the cloud infrastructure and in response to tracking the level objectives, determining a scaling decision associated with the application service, the scaling decision comprising either an upscaling or a downscaling;

in response to determining the scaling decision, implementing the scaling decision to match the level objectives associated with the cloud infrastructure and associated with the application service;

receiving an alert associated with a firewall attack on the application service; and

in response to receiving the alert:

identifying custom remediation actions established by an application service developer; and

deploying the custom remediation action, wherein the custom remediation action is configured to determine an extent of the firewall attack on an application boundary of the application service.

2 . The method of claim 1 , wherein the application service is deployed as a plurality of service instances across the cloud infrastructure, wherein the method further comprises, in response to tracing each action implemented in the cloud infrastructure during deployment, and in response to tracking level objectives:

identifying volume requests across the plurality of service instances;

consolidating resource requirements across the cloud infrastructure; and

providing recommendations to reduce a number of the plurality of service instances to a comparatively smaller number of larger service instances, wherein each larger service instance comprises at least two service instances of the plurality of service instances.

3 . The method of claim 1 , further comprising:

detecting incidents that arise during deployment of the application service by the cloud infrastructure; and

registering the incidents in one of a plurality of registries comprising an error registry that registers occurrence of errors and a remediation action registry that comprises instructions on executing remediation actions in response to errors.

4 . The method of claim 3 , further comprising deploying a handler component configured to wire each incident to a remediation action executable responsive to the occurrence of the incident.

5 . The method of claim 1 , further comprising:

consuming, by a de-bloater component, a plurality of service metrics and auto-scaler metrics derived from a plurality of service instances;

based on the consumed metrics, computing a recommended instance size and a recommended instance count to consolidate the plurality of service instances into a smaller number of larger service instances; and

providing the recommended instance size and recommended instance count to a controller to apply a new configuration.

6 . The method of claim 1 , further comprising:

injecting a chaos component into the application service during deployment of the application service by the cloud infrastructure, wherein the chaos component causes a deviation of operation of the application service; and

in response to injecting the chaos component, determining the deviation of the operation of the application service.

7 . The method of claim 6 , wherein the chaos component is injected during an application service upgrade and not during regular operation of the application service.

8 . The method of claim 1 , further comprising, during deployment of the application service by the cloud infrastructure, tracking power consumption trends of the cloud infrastructure by measuring power consumption by the application service.

9 . A non-transitory computer-readable medium storing instructions which, when executed by a hardware-based processor, performs operations comprising:

tracing each action implemented in the cloud infrastructure during deployment, by the cloud infrastructure of an application service, from an initiation of the application service to a termination of the application service;

tracking level objectives associated with the cloud infrastructure and associated with the application service deployed by the cloud infrastructure;

in response to tracing an action implemented in the cloud infrastructure and in response to tracking the level objectives, determining a scaling decision associated with the application service, the scaling decision comprising either an upscaling or a downscaling;

in response to determining the scaling decision, implementing the scaling decision to match the level objectives associated with the cloud infrastructure and associated with the application service;

receiving an alert associated with a firewall attack on the application service; and

in response to receiving the alert:

identifying custom remediation actions established by an application service developer; and

deploying the custom remediation action, wherein the custom remediation action is configured to determine an extent of the firewall attack on an application boundary of the application service.

10 . The medium of claim 9 , wherein the application service is deployed as a plurality of service instances across the cloud infrastructure, wherein the operations further comprise, in response to tracing each action implemented in the cloud infrastructure during deployment, and in response to tracking level objectives:

identifying volume requests across the plurality of service instances;

consolidating resource requirements across the cloud infrastructure; and

providing recommendations to reduce a number of the plurality of service instances to a comparatively smaller number of larger service instances, wherein each larger service instance comprises at least two service instances of the plurality of service instances.

11 . The medium of claim 9 , wherein the operations further comprise:

detecting incidents that arise during deployment of the application service by the cloud infrastructure; and

registering the incidents in one of a plurality of registries comprising an error registry that registers occurrence of errors and a remediation action registry that comprises instructions on executing remediation actions in response to errors.

12 . The medium of claim 11 , wherein the operations further comprise deploying a handler component configured to wire each incident to a remediation action executable responsive to the occurrence of the incident.

13 . The medium of claim 9 , wherein, the operations further comprising:

consuming, by a de-bloater component, a plurality of service metrics and auto-scaler metrics derived from a plurality of service instances;

based on the consumed metrics, computing a recommended instance size and a recommended instance count to consolidate the plurality of service instances into a smaller number of larger service instances; and

providing the recommended instance size and recommended instance count to a controller to apply a new configuration.

14 . The medium of claim 9 , wherein the operations further comprise:

injecting a chaos component into the application service during deployment of the application service by the cloud infrastructure, wherein the chaos component causes a deviation of operation of the application service; and

in response to injecting the chaos component, determining the deviation of the operation of the application service.

15 . The medium of claim 14 , wherein the chaos component is injected during an application service upgrade and not during regular operation of the application service.

16 . The medium of claim 9 , wherein the operations further comprise, during deployment of the application service by the cloud infrastructure, tracking power consumption trends of the cloud infrastructure by measuring power consumption by the application service.

17 . A system comprising:

one or more processors including a hardware-based processor; and

a memory storage including a non-transitory computer-readable medium storing instructions which, when executed by the one or more processors including the hardware-based processor, performs operations comprising:

tracing each action implemented in the cloud infrastructure during deployment, by the cloud infrastructure of an application service, from an initiation of the application service to a termination of the application service;

tracking level objectives associated with the cloud infrastructure and associated with the application service deployed by the cloud infrastructure;

in response to tracing an action implemented in the cloud infrastructure and in response to tracking the level objectives, determining a scaling decision associated with the application service, the scaling decision comprising either an upscaling or a downscaling;

in response to determining the scaling decision, implementing the scaling decision to match the level objectives associated with the cloud infrastructure and associated with the application service;

receiving an alert associated with a firewall attack on the application service; and

in response to receiving the alert:

identifying custom remediation actions established by an application service developer; and

deploying the custom remediation action, wherein the custom remediation action is configured to determine an extent of the firewall attack on an application boundary of the application service.

18 . The system of claim 17 , wherein the application service is deployed as a plurality of service instances across the cloud infrastructure, wherein the operations further comprise, in response to tracing each action implemented in the cloud infrastructure during deployment, and in response to tracking level objectives:

identifying volume requests across the plurality of service instances;

consolidating resource requirements across the cloud infrastructure; and

providing recommendations to reduce a number of the plurality of service instances to a comparatively smaller number of larger service instances, wherein each larger service instance comprises at least two service instances of the plurality of service instances.

19 . The system of claim 17 , wherein the operations further comprise:

detecting incidents that arise during deployment of the application service by the cloud infrastructure; and

registering the incidents in one of a plurality of registries comprising an error registry that registers occurrence of errors and a remediation action registry that comprises instructions on executing remediation actions in response to errors.

20 . The system of claim 17 , the operations further comprising:

consuming, by a de-bloater component, a plurality of service metrics and auto-scaler metrics derived from a plurality of service instances;

based on the consumed metrics, computing a recommended instance size and a recommended instance count to consolidate the plurality of service instances into a smaller number of larger service instances; and

providing the recommended instance size and recommended instance count to a controller to apply a new configuration.

Assignments (2)
CHANGE OF NAME Recorded May 8, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067355/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 18, 2022
From: BENJAMIN, EMAD; MONCLUS, PERE; CHANDRABOSE, DIWAN; PATHARKAR, ABHIJIT; MALLELA, ABHIRAMA
To: VMWARE, INC.
Reel/Frame 061818/0826 →
Priority Claims (1)
IN 202241041046 · Jul 18, 2022 · national
Continuity (1)
Related Publication 20240020185A1 · Jan 18, 2024
References Cited (5)
US 11997130B2 · Xu · 2024 [cited by examiner]
US 20190238561A1 · McGloin · 2019 [cited by examiner]
US 20220417257A1 · Behl · 2022 [cited by examiner]
US 20230179569A1 · Giralte · 2023 [cited by examiner]
US 20230247003A1 · Chanak · 2023 [cited by examiner]