Microservice Centrality Calculation for Data Center Workload Prioritization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data centers, especially on-premise and edge computing environments, face challenges in managing microservices during peak activity periods due to insufficient compute resources, leading to performance degradation, and struggle to prioritize workloads effectively as they consist of various process flows with differing criticalities.

Innovation Solution

A method and system for data center monitoring and management that identify and prioritize process flows with weighted priorities, map microservices associated with these flows, and calculate centrality values to optimize resource allocation and autoscaling, ensuring critical workloads receive adequate resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If compute resources are increased to handle peak activity periods, then service availability is improved, but cost and resource consumption increase

Engineering Contradiction:
Improveservice availabilityVSAvoidcompute resources
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system dynamically adjusts microservice instance counts based on real-time workload analysis and predicted activity patterns. During peak periods, the system automatically scales up critical microservices while maintaining optimal resource allocation, avoiding the need for continuous high resource consumption. This dynamic scaling resolves the contradiction by providing high availability only when needed while reducing resource usage during normal periods.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes operational parameters of microservices based on workload priority and predicted activity. By adjusting parameters such as instance count, resource allocation, and scaling thresholds based on process flow criticality and historical patterns, the system optimizes the balance between service availability and resource consumption without requiring static over-provisioning.

Inventive Principle:
Principle #35Parameter changes

2Device complexity

If all microservices are treated equally without prioritization, then system simplicity is maintained, but workload criticality cannot be addressed effectively

Engineering Contradiction:
Improvemanagement simplicityVSAvoidworkload prioritization
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system applies different quality levels of monitoring and management to different microservices based on their criticality. By analyzing process flow dependencies and workload characteristics, the system identifies critical microservices that require enhanced resource allocation and monitoring, while less critical services receive standard treatment. This local differentiation resolves the contradiction by providing targeted prioritization rather than uniform treatment across all services.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system segments microservices into priority groups based on their importance to business-critical process flows. This segmentation allows the system to apply differentiated resource allocation and management strategies to each segment, enabling effective workload prioritization while maintaining manageable complexity through automated classification rather than manual configuration.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If manual workload prioritization is performed, then customization to business needs is improved, but operational complexity and time consumption increase

Engineering Contradiction:
Improveworkload prioritization customizationVSAvoidoperational time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system automatically performs workload analysis and prioritization by monitoring process flow execution patterns, error rates, and resource consumption. It self-adjusts microservice priorities based on observed behavior and historical data, eliminating the need for manual configuration. This self-service approach provides customized prioritization adapted to actual business needs while consuming minimal operational time, as the system learns and adapts autonomously.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system continuously monitors workload performance and resource usage, using this feedback to dynamically adjust microservice priorities. By analyzing real-time metrics and comparing them against business objectives, the system automatically refines its prioritization strategy. This feedback mechanism enables highly customized prioritization that adapts to changing business needs without requiring manual reconfiguration, resolving the time consumption issue.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12021696B2Data center monitoring and management operation including microservice centrality calculation operation
Publication Date: 2024.06.25 DELL PROD LP
  • US12021696B2 patent drawing
  • US12021696B2 patent drawing
  • US12021696B2 patent drawing

AI summary

A system, method, and computer-readable medium for performing a data center management and monitoring operation. The data center management and monitoring operation includes: identifying a plurality of process flows, each of the plurality of process flows having a trace identifier and a corresponding weighted priority; identifying a plurality of microservices associated with each of the plurality of process flows; mapping each of the plurality of microservices associated with each of the plurality of process flows; and, calculating a centrality value for each of the plurality of microservices associated with each of the plurality of process flows based upon the mapping.