Declarative Workflow Orchestration Across Cloud Providers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud computing systems lack user-friendly and efficient methods for orchestrating serverless functions across multiple cloud providers, requiring users to code and manage workflows independently, which is not reusable and burdensome.

Innovation Solution

A system and method for executing workflow definitions across multiple cloud services providers by determining the executable provider for each function definition and invoking the appropriate provider function, allowing for provider-agnostic orchestration of serverless functions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users code and run workflows independently from cloud computing providers, then cross-provider function orchestration is achieved, but user burden and complexity increase

Engineering Contradiction:
Improvecross-provider function orchestration capabilityVSAvoidworkflow management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary workflow definition language and orchestration mechanism that sits between users and multiple cloud providers. This intermediary layer translates high-level workflow definitions into provider-specific function invocations, enabling cross-provider orchestration without requiring users to manage the complexity of each provider's native interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal workflow definition framework that can orchestrate functions across different cloud providers (AWS Lambda, Azure Functions, Google Cloud Functions, etc.) through a single unified interface. This universal approach allows the same workflow definition to execute across multiple providers without modification, eliminating the need for provider-specific coding.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If proprietary orchestration approaches are used by each cloud provider, then platform-specific optimization is achieved, but cross-provider orchestration capability is lost

Engineering Contradiction:
Improveplatform-specific execution reliabilityVSAvoidcross-provider orchestration capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The workflow definition language acts as an intermediary that preserves platform-specific execution reliability while enabling cross-provider capability. It maintains abstract function definitions that can be executed on any supported platform through provider-specific adapters, thus achieving both reliability and versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the orchestration system into two parts: a provider-agnostic workflow definition layer and provider-specific execution adapters. This segmentation allows each layer to optimize for its specific purpose while working together to achieve cross-provider functionality.

Inventive Principle:
Principle #1Segmentation

3Productivity

If custom scripts are written to orchestrate functions across providers, then workflow execution is achieved, but reusability and ease of operation decrease

Engineering Contradiction:
Improveworkflow execution capabilityVSAvoidworkflow creation ease
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent uses template-based workflow definitions that can be copied and reused across different providers and scenarios. Instead of writing custom scripts from scratch, users can define workflows once in the declarative language and reuse them across multiple cloud providers, significantly improving ease of operation and reusability.

Inventive Principle:
Principle #26Copying

4Extent of automation

If users manage infrastructure to support orchestration, then workflow control is achieved, but maintenance burden increases

Engineering Contradiction:
Improveworkflow execution controlVSAvoidorchestration infrastructure maintenance
Core Design Contradiction:
Extent of automationVSEase of manufacture

Solution Approach 1:

The patent enables workflows to be self-describing and self-executing through the declarative definition language. The workflow definitions contain all necessary information for execution, and the system automatically handles provider-specific adaptations, eliminating the need for users to manually manage orchestration infrastructure.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11182218B2Method and apparatus for orchestrating cross-FaaS provider functions declaratively
Publication Date: 2021.11.23 VMWARE INC
  • US11182218B2 patent drawing
  • US11182218B2 patent drawing
  • US11182218B2 patent drawing

AI summary

System and computer-implemented method for executing a workflow definition with a set of function definitions having code executable with at least one cloud services provider in a plurality of cloud services providers involve reception of a request to execute a function definition from the workflow definition and a determination of whether code contained in the function definition is only executable at that particular cloud services provider. A provider function at the cloud services provider is invoked using the function definition and an execute command for the provider function is transmitted for the provider function.