Cloud Application Redeployment via Inventory Module

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud computing management approaches often result in underutilized, over-constrained, or expensive application deployments due to a one-size-fits-all management of cloud services and applications, leading to inadequate flexibility and cost inefficiencies.

Innovation Solution

A method and system that deploy applications across multiple cloud computing environments, utilizing an inventory module to identify available instances of services, allowing for redeployment and optimization of services across platforms to maximize utilization and reduce costs by redistributing services based on policies such as cost and performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If a one-size-fits-all approach is used to manage cloud services and applications in a centralized cloud computing environment, then service deployment is simplified, but resource utilization becomes inefficient and costs increase

Engineering Contradiction:
Improveservice deployment simplicityVSAvoidresource utilization efficiency
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The system segments cloud services into multiple independent instances across different cloud computing environments. Instead of managing services as a single centralized entity, the invention divides service instances across multiple clouds (e.g., Cloud A, Cloud B, Cloud C), allowing independent management and optimization of each instance. This segmentation enables efficient resource utilization by selecting appropriate instances based on current availability and performance metrics.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically changes parameters such as service instance selection, cloud environment allocation, and resource distribution based on real-time conditions. The service composition manager adjusts which service instances are deployed to which applications, modifying deployment parameters to optimize resource utilization while maintaining service functionality across different cloud environments.

Inventive Principle:
Principle #35Parameter changes

2Device complexity

If services are centralized in a single cloud computing environment, then management is simplified, but system reliability decreases when services become unavailable

Engineering Contradiction:
Improvemanagement complexityVSAvoidservice availability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system merges multiple cloud computing environments into a unified service delivery platform. By combining services from different cloud providers (e.g., AWS, Azure, Google Cloud) into a single managed ecosystem, the invention achieves both simplified management through centralized orchestration and improved reliability through distributed service instances. The service composition manager coordinates across merged cloud environments to maintain service availability.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system creates and maintains multiple copies of service instances across different cloud computing environments. Instead of relying on a single service instance, the invention deploys replicated service copies in multiple clouds, ensuring that if one instance becomes unavailable, another copy can immediately take over. This copying strategy maintains service continuity while the service composition manager handles the complexity of coordinating these replicas.

Inventive Principle:
Principle #26Copying

3Reliability

If multiple service instances are maintained across different cloud computing environments, then service reliability improves, but management complexity increases

Engineering Contradiction:
Improveservice availabilityVSAvoidservice management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The service composition manager acts as an intermediary layer between applications and multiple service instances across different cloud environments. This mediator abstracts the complexity of managing distributed service instances by providing a unified interface for service discovery, selection, and orchestration. The intermediary handles instance registration, health monitoring, and failover logic, shielding application developers from the underlying management complexity while maintaining high service availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If cloud services are used with a one-size-fits-all management approach, then deployment speed is fast, but cost efficiency decreases

Engineering Contradiction:
Improvedeployment speedVSAvoidcost efficiency
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system implements dynamic service instance selection and allocation that adapts to changing conditions in real-time. Instead of static, one-size-fits-all deployment configurations, the service composition manager continuously monitors service performance, availability, and cost metrics across multiple cloud environments, dynamically selecting and allocating service instances to optimize both deployment speed and cost efficiency based on current conditions.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10620928B2Global cloud applications management
Publication Date: 2020.04.14 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10620928B2 patent drawing
  • US10620928B2 patent drawing
  • US10620928B2 patent drawing

AI summary

Systems, methods, and computer program products to perform an operation comprising deploying a first application in a first cloud computing environment of a plurality of cloud computing environments, wherein the first application is composed of a first instance of a first service, determining that the first service has become unavailable in the first cloud computing environment, identifying, by an instance of inventory module executing in the first cloud computing environment, a second instance of the first service in one of the plurality of cloud computing environments, building the first application using the second instance of the first service; and redeploying the first application built using the second instance of the first service in the first cloud computing environment.