Cloud Automation Throttling for Resource Conflict Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional automations on cloud platforms often run without restrictions, leading to high-resource usage and impact on applications or resources utilized by clients, resulting in reduced availability for primary applications.

Innovation Solution

Implement resource throttling and operation staggering services to manage the number and timing of automations, ensuring they stay within defined limits and staggered start times to maintain consistent resource distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If automations are allowed to run without restrictions, then automation productivity is improved, but resource availability for client applications deteriorates

Engineering Contradiction:
Improveautomation productivityVSAvoidresource availability for client applications
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

A resource throttling service is introduced as an intermediary between automations and cloud platform resources. This service manages and regulates resource access by automations, ensuring they operate within defined limits while maintaining resource availability for client applications. The throttling service acts as a mediator that balances automation needs with client application requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple automations run concurrently, then automation throughput is improved, but resource conflicts and interference between automations increase

Engineering Contradiction:
Improveautomation throughputVSAvoidresource conflicts between automations
Core Design Contradiction:
ProductivityVSObject-generated harmful factors

Solution Approach 1:

The system performs preliminary actions by checking for resource conflicts before allowing automations to execute. The resource throttling service proactively identifies potential conflicts and prevents them before they occur, rather than reacting to conflicts after they manifest. This advance preparation enables higher automation throughput while minimizing resource conflicts.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The resource throttling service implements feedback mechanisms that continuously monitor resource usage and automation execution. Based on this feedback, the service dynamically adjusts automation scheduling and resource allocation to prevent conflicts and optimize throughput, creating a closed-loop system that adapts to changing conditions.

Inventive Principle:
Principle #23Feedback

3Extent of automation

If automation resource usage is increased, then automation functionality is improved, but impact on client applications deteriorates

Engineering Contradiction:
Improveautomation functionalityVSAvoidimpact on client applications
Core Design Contradiction:
Extent of automationVSObject-affected harmful factors

Solution Approach 1:

The system changes critical parameters related to resource allocation and automation execution. By dynamically adjusting parameters such as resource quotas, execution timing, and concurrency limits, the resource throttling service enables enhanced automation functionality while controlling the impact on client applications through controlled parameter modification rather than fixed rigid limits.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12474965B2Resource and operation conflict identification on a cloud platform
Publication Date: 2025.11.18 SERVICENOW INC
  • US12474965B2 patent drawing
  • US12474965B2 patent drawing
  • US12474965B2 patent drawing

AI summary

Various approaches are described to manage the execution of operations. Such operations may be performed without human intervention and may help maintain functionality of a cloud platform or client instances. In one aspect of the present approach, the number and/or type of automations starting in a given time frame may be limited to maintain an even or consistent distribution of resource usage. In a further aspect, the number and/or type of concurrent automations may be limited to a defined threshold to maintain an even or consistent distribution of resource usage.