Cloud Release Orchestration Using Portable Execution Plans

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Deploying software releases on multiple cloud platforms is complex due to differences in tools and requirements, leading to high maintenance costs for multi-tenant systems, especially when managing services for numerous data centers with varying software, languages, and network policies across diverse cloud platforms.

Innovation Solution

A cloud platform infrastructure language allows for substrate-independent orchestration of software releases using declarative specifications, enabling the generation of execution plans that are portable across various cloud platforms, and includes features like stagger groups, promotion strategies, and notification mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple cloud platforms are supported with different tools and requirements, then platform compatibility is improved, but maintenance cost and complexity increase

Engineering Contradiction:
Improveplatform compatibilityVSAvoidmaintenance cost
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal orchestration layer that provides a common interface and standardized processes for deploying software releases across multiple cloud platforms. This abstraction layer enables the system to work with different cloud providers (AWS, Azure, GCP, etc.) through unified mechanisms, eliminating the need for separate maintenance procedures for each platform and reducing overall complexity.

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

Solution Approach 2:

The patent introduces an intermediary orchestration component that sits between the deployment system and various cloud platforms. This mediator translates standardized deployment requests into platform-specific actions, handling differences in tools and requirements internally while presenting a consistent interface to users, thereby reducing maintenance burden.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If different implementations are maintained for each cloud platform, then platform-specific requirements are met, but expertise requirements and operational complexity increase

Engineering Contradiction:
Improveplatform-specific supportVSAvoidexpertise requirements
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The orchestration layer provides unified mechanisms for release deployment, rollback, and management that work across all supported cloud platforms. Operators can perform standard deployment tasks using a single set of procedures and tools, eliminating the need to learn and maintain separate implementations for each cloud provider.

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

3Productivity

If software releases are deployed across numerous data centers with varying requirements, then service coverage is improved, but deployment complexity increases

Engineering Contradiction:
Improveservice coverageVSAvoiddeployment complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the deployment process into standardized, modular stages that can be consistently applied across numerous data centers. By dividing the complex deployment task into discrete, manageable steps with uniform procedures, the system can scale to serve many data centers without proportionally increasing operational complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12498914B2Orchestration of software releases on a cloud platform
Publication Date: 2025.12.16 SALESFORCE INC
  • US12498914B2 patent drawing
  • US12498914B2 patent drawing
  • US12498914B2 patent drawing

AI summary

A multi-tenant system receives a request to build a software artifact for deploying on one or more target datacenter entities of the datacenter configured on the could platform. A software artifact comprises executable instructions associated with a service configured for execution on one or more cloud platforms. The system generates a release configuration that includes reusable release components and is used as a template by the release orchestration system to orchestrate release of the software artifact. In one embodiment, the release configuration includes a variable representing a placeholder for one or more elements of the release.