Cloud Service Instance Pool Management for Provisioning Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing cloud computing systems face delays and inefficiencies in provisioning services due to time-consuming instance creation processes, especially under high demand, and imprecise capacity management, leading to inadequate resource allocation and delays in service availability.

Innovation Solution

Implementing a system that proactively constructs and maintains pools of pre-provisioned and pre-orchestrated instances, allowing for quick provisioning of executing instances by executing pre-configured computing environments and software, and using feedback loops for dynamic capacity management across zones.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If on-demand instance creation is used for cloud services, then service flexibility and accessibility are improved, but provisioning time increases significantly

Engineering Contradiction:
Improveservice flexibilityVSAvoidprovisioning time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system pre-provisions and pre-orchestrates service instances before they are actually needed. When a service request arrives, the instance is already prepared and can be activated immediately, eliminating the lengthy provisioning process that would otherwise be required during the request fulfillment phase.

Inventive Principle:
Principle #10Preliminary action

2Ease of manufacture

If traditional instance provisioning is used, then resource allocation is simplified, but service availability is delayed under high demand

Engineering Contradiction:
Improveresource allocation simplicityVSAvoidservice availability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

Instances are pre-provisioned and pre-orchestrated in advance, so when demand occurs, the infrastructure is already in place and ready for immediate activation, ensuring service availability without delays.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors service demand patterns and uses this feedback to dynamically adjust the pool of pre-provisioned instances, ensuring adequate resource allocation matches actual demand while maintaining simple automated management.

Inventive Principle:
Principle #23Feedback

3Productivity

If pre-provisioned instances are maintained in pools, then provisioning speed increases, but system complexity increases

Engineering Contradiction:
Improveprovisioning speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system automatically manages the pools of pre-provisioned instances through self-service mechanisms, including self-provisioning, self-monitoring, and self-adjustment based on demand patterns, eliminating the need for manual intervention and reducing operational complexity despite the increased structural complexity.

Inventive Principle:
Principle #25Self-service

4Measurement precision

If capacity management is performed manually, then control precision is maintained, but response time to demand changes increases

Engineering Contradiction:
Improvecapacity management precisionVSAvoidresponse time
Core Design Contradiction:
Measurement precisionVSSpeed

Solution Approach 1:

The system implements automated feedback loops that continuously monitor service demand, resource utilization, and instance performance, dynamically adjusting capacity allocation in real-time to match actual demand patterns with precise speed and accuracy.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10911367B2Computerized methods and systems for managing cloud computer services
Publication Date: 2021.02.02 ORACLE INT CORP
  • US10911367B2 patent drawing
  • US10911367B2 patent drawing
  • US10911367B2 patent drawing

AI summary

Systems, methods, and other embodiments associated with managing instances of services are described. In one embodiment, a method includes constructing pre-provisioned instances of a service within a first pool and constructing pre-orchestrated instances of the service within a second pool. In response to receiving a request for the service, the method executes executable code of a first pre-orchestrated instance as an executing instance and removing the pre-orchestrated instance from the second pool. A pre-provisioned instance is selected from the first pool to create a second pre-orchestrated instance within the second pool, and the pre-provisioned instance is removed from the first pool.