Autoscaling Engine for Cloud Resource Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud service providers face challenges in efficiently scaling cloud resources to meet varying demand, leading to over-provisioning and increased costs or under-provisioning that violates service level agreements, as existing systems lack effective autoscaling capabilities across diverse resource types.

Innovation Solution

An autoscaling system that includes a processor and memory, configured to define and execute autoscale policies for multiple resource types, such as virtual machines, container instances, and data storage, using capacity data and metric-based rules to selectively scale in or out, ensuring compliance with service level agreements and optimizing resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If capacity is allocated based on peak usage to ensure service level agreements are met, then performance reliability is improved, but resource cost increases due to over-provisioning

Engineering Contradiction:
Improveservice level agreement complianceVSAvoidresource allocation
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system implements dynamic capacity allocation that automatically adjusts resource provisioning based on real-time demand conditions. The autoscaling engine continuously monitors workload metrics and modifies capacity levels dynamically, transitioning from static peak-based provisioning to adaptive demand-based provisioning, thereby optimizing the balance between reliability and resource efficiency

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system employs feedback mechanisms where capacity allocation decisions are continuously refined based on monitored performance data and workload patterns. The autoscaling engine uses feedback from capacity metrics and workload analysis to adjust provisioning levels, ensuring service level agreement compliance while preventing over-provisioning through data-driven decision making

Inventive Principle:
Principle #23Feedback

2Quantity of substance

If capacity is reduced to save costs, then resource expenditure decreases, but service level agreements may be violated and performance suffers during peak usage

Engineering Contradiction:
Improveresource allocationVSAvoidservice level agreement compliance
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system performs preliminary analysis of workload patterns and capacity requirements to make proactive scaling decisions. By analyzing historical and real-time data, the autoscaling engine anticipates demand changes and adjusts capacity before performance degradation occurs, preventing SLA violations while optimizing resource utilization

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes operational parameters by adjusting capacity levels based on multiple factors including workload intensity, growth trends, and service level requirements. The autoscaling engine dynamically modifies provisioning parameters to achieve cost optimization without compromising reliability, using parameter adjustments rather than fixed allocation rules

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If autoscaling is implemented across multiple resource types, then system adaptability improves, but calculation complexity increases due to interdependencies

Engineering Contradiction:
Improvemulti-resource type supportVSAvoidscaling calculation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the autoscaling problem by analyzing each resource type independently while considering their interdependencies. The evaluation engine divides complex multi-resource scaling decisions into manageable components, assessing capacity and workload metrics for each resource type separately before integrating results, thereby reducing calculation complexity while maintaining comprehensive adaptability

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10547672B2Anti-flapping system for autoscaling resources in cloud networks
Publication Date: 2020.01.28 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10547672B2 patent drawing
  • US10547672B2 patent drawing
  • US10547672B2 patent drawing

AI summary

An autoscaling system for scaling resource instances in a cloud network includes an autoscaling application is stored in memory and executed by a processor. The autoscaling application is configured to provide an interface to define an autoscale policy including scale in rules and scale out rules for a plurality of different types of resource instances of a tenant. The autoscaling application is configured to receive capacity data corresponding to a first type of the plurality of different types of resource instances; calculate an estimated instance count for scaling in the first type based on the capacity data and scale in rules; calculate a projection factor based on an estimated instance count and a current instance count; generate adjusted capacity data based on current capacity data and the projection factor; compare the adjusted capacity data and the scale out rules; and selectively scale in the first type based on the comparison.