Cloud Service Update Deployment via Segmented Installer Instances

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current approaches to deploying updates in cloud-based services are sequential, leading to a single point of failure and significant delays if a regression is introduced, affecting the entire deployment framework.

Innovation Solution

A scalable deployment framework that automatically adapts to changing deployment policies and ring structures, allowing for parallel deployment of updates across multiple rings and stages, with load balancing to distribute tasks and rapid recovery from failed updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If updates are deployed sequentially across cloud-based service systems, then deployment control and risk mitigation are improved, but deployment time and system availability deteriorate significantly when regressions occur

Engineering Contradiction:
Improvedeployment controlVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent divides the deployment system into independent installer instances, each responsible for specific rings or stages. This segmentation allows parallel deployment across multiple segments while maintaining individual control, so that a failure in one segment does not halt deployments in other segments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from sequential deployment (one dimension) to parallel deployment across multiple installer instances (adding another dimension). This dimensional change enables simultaneous deployment to multiple rings while maintaining risk mitigation through independent instance management.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Productivity

If multiple versions of updates are deployed simultaneously to different rings, then productivity and deployment speed are improved, but system reliability deteriorates due to single point of failure

Engineering Contradiction:
Improvedeployment speedVSAvoidsystem availability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The deployment framework is segmented into multiple independent installer instances, each capable of deploying updates to specific rings. This segmentation enables parallel deployment (improving productivity) while isolation between instances prevents single points of failure (maintaining reliability).

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically adjusts deployment parameters such as ring assignments and payload selections for each installer instance based on policy information. This allows flexible configuration of parallel deployments while maintaining control over reliability through parameter-based instance management.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If a regression is introduced in one update version, then deployment control is maintained for that version, but the entire deployment framework becomes incapacitated

Engineering Contradiction:
Improvedeployment controlVSAvoiddeployment capability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

By segmenting the deployment framework into independent installer instances, the patent ensures that a regression affecting one instance does not incapacitate the entire system. Other instances continue to deploy their assigned updates independently, maintaining overall deployment capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a configuration store as an intermediary between policy information and installer instances. This intermediary allows dynamic adjustment of instance configurations and ring assignments, enabling the system to maintain deployment control while isolating the impact of regressions to specific instances.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Stability of the object's composition

If sequential deployment is used to mitigate risk, then deployment stability is improved, but the ability to rapidly deploy fixes and new features deteriorates

Engineering Contradiction:
Improvedeployment stabilityVSAvoiddeployment rate
Core Design Contradiction:
Stability of the object's compositionVSSpeed

Solution Approach 1:

The patent segments the deployment process into parallel installer instances that can simultaneously deploy to different rings. This segmentation maintains stability through independent instance management while dramatically increasing the overall deployment rate through parallel execution.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system adds a parallel dimension to deployment by running multiple installer instances simultaneously. This dimensional change enables rapid deployment across multiple rings while maintaining stability through the independent, isolated nature of each instance.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS20250165244A1Partitioned deployment of updates to cloud service based on centerally updated configuration store
Publication Date: 2025.05.22 MICROSOFT TECHNOLOGY LICENSING LLC
  • US20250165244A1 patent drawing
  • US20250165244A1 patent drawing
  • US20250165244A1 patent drawing

AI summary

A data processing system implements obtaining policy information for an update to be deployed to one or more components of a cloud-based service identifying a plurality of rings of the cloud-based service to which the update is to be deployed; analyzing the policy information to determine configuration information for a plurality of installer instances each associated with one or more rings or one or more stages of a ring to which the update is to be deployed; obtaining payload information for each respective installer instance, the payload information indicating one or more payloads associated with the update to be deployed to the respective one or more rings or one or more stages of the ring associated with the respective installer instance; and deploying the one or more payloads for each of the one or more rings or the one or more stages of the ring associated with each installer instance.