Workload-Based Service Classification in Cloud Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems fail to dynamically schedule operational decisions based on service workloads, leading to operational and stability risks when updating software, allocating resources, and triaging incidents across thousands of highly-available stateful services in cloud environments.

Innovation Solution

A computer-implemented method that collects metrics for service instances, uses machine learning algorithms like k-means clustering and neural networks to classify them, and performs operational decisions such as load balancing and security updates to minimize risk and maximize uptime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional systems update software, allocate resources, or triage incidents across thousands of services, then operational decisions are made, but stability and availability deteriorate due to lack of dynamic workload consideration

Engineering Contradiction:
Improvestability and availabilityVSAvoidoperational decision-making
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system dynamically classifies services into workload categories (batch, transactional, analytical) based on real-time metric analysis, enabling operational decisions to adapt to current workload conditions rather than following static procedures. This dynamic classification allows the system to adjust operational intensity and timing based on actual service state.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system continuously collects metrics from services and uses machine learning models to classify workloads, creating a feedback loop where operational decisions are informed by real-time performance data. This feedback mechanism enables the system to learn from past operational outcomes and improve future decision-making.

Inventive Principle:
Principle #23Feedback

2Reliability

If systems perform operational decisions without workload-based classification, then processes are simplified, but operational risk increases due to inadequate risk assessment

Engineering Contradiction:
Improveoperational riskVSAvoidclassification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments services into distinct workload categories (batch processing, transactional, analytical) based on their operational characteristics. This segmentation allows different risk management strategies to be applied to different service types, reducing overall operational risk while managing complexity through structured classification.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The machine learning classification system acts as an intermediary layer between raw service metrics and operational decision-making. This intermediary translates complex multi-dimensional service data into simplified workload categories that can be directly used for risk assessment and operational planning.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If systems respond to service incidents without real-time workload analysis, then response processes are faster, but response quality deteriorates due to lack of informed decision-making

Engineering Contradiction:
Improveworkload pattern recognitionVSAvoidoperational response time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary classification of services into workload categories before incidents occur, using machine learning models trained on historical metric data. This preliminary action ensures that when incidents happen, the system already has pre-computed workload classifications ready for immediate use in incident response.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes the parameter of service classification from static to dynamic by continuously updating workload categories based on real-time metric analysis. This allows the system to recognize subtle changes in service behavior patterns and adjust operational responses accordingly.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20240386033A1Workload-based classification of services
Publication Date: 2024.11.21 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US20240386033A1 patent drawing
  • US20240386033A1 patent drawing
  • US20240386033A1 patent drawing

AI summary

A method, system, and computer program product that is configured to: collect a plurality of metrics for running service instances within a cloud-based system; classify the running service instances into a database classification using a machine learning algorithm based on the collected plurality of metrics for the running service instances; and perform at least one operational decision corresponding to the classified running service instances.