Cloud Service Migration Planning with Edit-Distance Log Similarity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud environments face issues such as overloading due to improper migration of online services, errors during migration, and delayed decision-making, leading to suboptimal resource utilization and service functionality.

Innovation Solution

A system computes edit distance values based on transaction log data to determine similarity between online services, creating a migration plan that balances load across multiple destination cloud environments, and verifies successful migration using checksums.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If online services are migrated to destination cloud environments to avoid overloading, then resource utilization is improved, but destination environments may become overloaded due to improper migration

Engineering Contradiction:
Improveresource utilizationVSAvoidservice functionality
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system continuously monitors resource utilization metrics in both source and destination cloud environments. This feedback mechanism enables dynamic adjustment of migration decisions, ensuring that services are migrated only when it improves overall resource utilization without causing overload at destination environments. The monitoring component tracks metrics such as CPU usage, memory consumption, and request rates to make informed migration decisions.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system changes the operational parameters of services by migrating them between different cloud environments based on computed similarity metrics. By analyzing transaction log data and calculating edit distance values, the system determines optimal migration targets that match service requirements with destination environment capabilities, thereby improving resource utilization while maintaining service reliability.

Inventive Principle:
Principle #35Parameter changes

2Speed

If migration decisions are made quickly to prevent overloading, then service continuity is improved, but errors may occur during migration

Engineering Contradiction:
Improvemigration speedVSAvoidmigration success
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system performs preliminary actions by computing edit distance values and determining service similarity metrics before initiating migration. This advance preparation includes analyzing transaction log data, identifying suitable destination environments, and validating migration feasibility. By completing these preliminary steps, the system ensures that migration decisions are both rapid and accurate, preventing both delays and errors.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service verification through checksum validation during the migration process. The verification component automatically checks the integrity of migrated services by comparing checksums of source and destination service states. This self-verification mechanism enables fast migration while maintaining high reliability, as errors are detected and corrected automatically without manual intervention.

Inventive Principle:
Principle #25Self-service

3Productivity

If services are migrated to balance load across destination environments, then resource allocation is optimized, but system complexity increases

Engineering Contradiction:
Improveresource allocation efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the complex migration task into distinct functional components: a monitoring component that collects resource metrics, a calculation component that computes edit distance values and similarity metrics, a verification component that validates migrations using checksums, and a migration execution component that performs the actual service migration. This segmentation reduces system complexity by assigning specific responsibilities to each component while achieving optimized resource allocation through their coordinated operation.

Inventive Principle:
Principle #1Segmentation

4Reliability

If multiple destination cloud environments are used to distribute services, then overloading is prevented, but migration planning complexity increases

Engineering Contradiction:
Improveservice availabilityVSAvoidmigration plan complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system uses parameter changes in the form of edit distance values derived from transaction log data to simplify migration planning across multiple destination environments. By transforming complex service characteristics into comparable numerical parameters, the system can efficiently evaluate and select optimal destination environments. This parameter-based approach maintains high service availability through load distribution while reducing migration plan complexity through standardized comparison metrics.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP4336362B1Dynamically migrating services based on similarity
Publication Date: 2026.01.14 SAP SE
  • EP4336362B1 patent drawingFigure 1
  • EP4336362B1 patent drawingFigure 2
  • EP4336362B1 patent drawingFigure 3

AI summary

Techniques for dynamically migrating services based on similarity are disclosed. In some embodiments, a computer system may, for each online service in a plurality of online services of a source cloud environment, compute a corresponding edit distance value based on a stream of transaction log data of the online service. The edit distance value may comprise a minimum number of edit operations required to change a first log entry in the stream of transaction log data to a second log entry in the stream of transaction log data. Next, the computer system may determine a migration plan based on a measure of similarity between the edit distance values of the online services, where the migration plan specifies a distribution of the online services amongst a plurality of destination cloud environments, and then migrate the online services from the source cloud environment to the destination cloud environments using the migration plan.