Multi-Cloud Operations Center for Function Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current techniques lack efficient methods for deploying and managing function-based applications across multiple cloud environments, particularly in terms of cost optimization, seamless migration, and unified billing, leading to complexity for developers.

Innovation Solution

A Multi-Cloud Operations Center is introduced, which provides a software architecture that enables developers to deploy, manage, and migrate function-based applications across multiple clouds with features like single user accounts, automatic URL redirection, Cloud-Aware Continuous Integration (CI) and Continuous Deployment (CD), and unified billing, simplifying the process and reducing human intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If function-based applications are deployed across multiple cloud environments, then service availability and flexibility are improved, but deployment complexity and management overhead increase

Engineering Contradiction:
Improvemulti-cloud deployment capabilityVSAvoiddeployment and management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a transpiler as an intermediary component that sits between the developer's source code and the multiple cloud environments. This transpiler automatically translates and adapts the source code to be compatible with different cloud platforms (AWS, Azure, GCP), eliminating the need for developers to manually adapt code for each cloud environment. The transpiler handles cloud-specific configurations, dependencies, and deployment requirements, thereby reducing deployment complexity while maintaining multi-cloud versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the deployment process into distinct components: source code writing, transpilation, and cloud-specific deployment. By separating the universal function logic from cloud-specific adaptations, the system allows developers to write platform-agnostic code while the transpiler handles cloud-specific segmentation. This segmentation reduces management overhead by isolating cloud complexity from the core application logic.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If manual code adaptation is performed for each cloud environment, then cloud-specific optimization is improved, but time consumption and human effort increase

Engineering Contradiction:
Improvecloud environment compatibilityVSAvoidcode adaptation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The transpiler performs preliminary actions by pre-configuring cloud-specific adaptations, dependencies, and deployment settings before the actual deployment process. It prepares the code in advance for target cloud environments, resolving cloud-specific configurations and dependencies ahead of time. This preliminary processing significantly reduces the time required for manual code adaptation and deployment preparation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service through automated transpilation that requires minimal human intervention. The transpiler autonomously analyzes source code, identifies cloud-specific requirements, and generates adapted code for different cloud platforms without requiring manual intervention from developers. This automation eliminates repetitive manual adaptation tasks while maintaining cloud-specific optimization.

Inventive Principle:
Principle #25Self-service

3Loss of energy

If multiple cloud environments are used, then cost optimization opportunities are improved, but billing management complexity increases

Engineering Contradiction:
Improvecost optimizationVSAvoidbilling management complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent merges multiple cloud billing systems into a unified billing interface. The system consolidates billing data from different cloud providers (AWS, Azure, GCP) and presents a single, unified bill to the customer. This merging approach maintains the cost optimization benefits of multi-cloud deployment while eliminating the complexity of managing separate billing relationships with multiple cloud providers. The unified billing system handles invoicing, payment processing, and cost allocation across all cloud environments through a single interface.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11055066B2Multi-cloud operations center for function-based applications
Publication Date: 2021.07.06 EMC IP HLDG CO LLC
  • US11055066B2 patent drawing
  • US11055066B2 patent drawing
  • US11055066B2 patent drawing

AI summary

Techniques are provided for a multi-cloud operations center for function-based applications. One method includes obtaining source code for a function of multiple functions of an application, where the function is hosted in a first cloud environment of multiple distinct cloud environments, generating adapted source code from the source code to migrate the function to a second cloud having a different cloud environment; and deploying the function to the second cloud having the different cloud environment using the adapted source code. The source code may be automatically updated for the at least one function for the multiple distinct cloud environments. The function may have a corresponding network address that identifies the function across multiple distinct cloud environments, and network address redirection is performed based on a given cloud environment on which the function is deployed.