Cloud Service Community Replication for Fast Load Pressure Shifting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud platform management methods struggle to quickly adjust load pressure, leading to limited performance when capacity expansion is performed on individual cloud service components, resulting in new hot points and increased load pressure on other components.
Innovation Solution
Group cloud service components into communities based on call relationships, and create additional communities when certain conditions are met to share load, using cloning and load balancing to adjust platform load pressure effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If capacity expansion is performed on individual cloud service components one by one, then the load of that specific component can be reduced, but the overall load pressure of the cloud platform cannot be quickly adjusted and new hot points may emerge
Solution Approach 1:
The patent segments cloud service components into communities based on call relationships and degree of closeness. Instead of treating individual components separately, the system groups them into communities where components with high inter-call frequency are clustered together. This segmentation enables load adjustment at the community level, allowing rapid redistribution of load across multiple components simultaneously, thus resolving the contradiction between reliable load balancing and fast load adjustment speed.
Solution Approach 2:
The patent creates a second community that is a copy of the first community when performance thresholds are met. This copying mechanism allows the system to rapidly replicate successful community configurations and distribute load across identical community structures. By copying communities rather than adjusting individual components, the system achieves quick load pressure adjustment while maintaining balanced distribution, preventing new hot points from emerging.
2Productivity
If cloud service components are grouped into communities based on call relationships, then load can be shared more effectively, but the system complexity increases due to community management
Solution Approach 1:
The patent applies universality by creating communities with standardized structures and interfaces. Each community functions as a multi-functional unit that can handle various types of cloud service components while following the same management protocols. The second community is created as a universal copy of the first, enabling consistent load sharing mechanisms across different community types. This standardization reduces management complexity despite the increased number of communities, as the same rules and procedures apply universally.
3Adaptability or versatility
If the degree of closeness threshold for community formation is lowered, then more components can be grouped into communities improving load distribution, but the number of communities increases making management more difficult
Solution Approach 1:
The patent uses parameter changes by dynamically adjusting the degree of closeness threshold based on system conditions. When load pressure is high, the threshold may be lowered to form more communities and improve load distribution flexibility. When the system is stable, the threshold can be raised to reduce the number of communities and simplify management. This dynamic parameter adjustment allows the system to adapt between flexibility and manageability based on operational needs, resolving the contradiction between load distribution adaptability and community management complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Embodiments of this application relate to the field of cloud computing, and provide a cloud platform management method and an apparatus, a program product, and a storage medium, to quickly adjust load pressure of a cloud platform. The method includes: grouping a plurality of cloud service components in a cloud platform into a plurality of communities based on call relationships between the plurality of cloud service components, where a degree of closeness of a call relationship between cloud service components included in each community is greater than or equal to a preset degree of closeness, and a degree of closeness between a cloud service component in any one of the plurality of communities and a cloud service component in another community is less than the preset degree of closeness; and if a target component in a first community of the plurality of communities meets a first preset condition, creating a second community, where the second community is the same as the first community, the second community is configured to share a part of load of the first community, the first preset condition indicates that performance of the target component is lower than preset performance, and the target component is at least one of a plurality of cloud service components in the first community.