Microservice Refactoring via Log Analysis for Resource Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in securing devices and efficiently utilizing computing resources, leading to increased attack surfaces and resource inefficiencies.

Innovation Solution

The system refactors services into microservices by analyzing logs to identify functional flows, discriminating source code portions, and compiling them into independently executable services, thereby reducing resource usage and attack surfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If services are run as monolithic units, then service functionality is maintained, but computing resource requirements increase and attack surfaces expand

Engineering Contradiction:
Improveservice functionalityVSAvoidcomputing resource requirements
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent divides monolithic services into smaller microservices by analyzing logs to identify functional flows, then discriminating source code portions corresponding to each flow. This segmentation allows only necessary microservices to be executed simultaneously, reducing computing resource requirements while maintaining overall service functionality through selective execution of individual microservices.

Inventive Principle:
Principle #1Segmentation

2Reliability

If services are run as monolithic units, then service functionality is maintained, but attack surfaces increase

Engineering Contradiction:
Improveservice functionalityVSAvoidattack surfaces
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

By segmenting the monolithic service into discrete microservices based on functional flows identified through log analysis, the patent reduces the attack surface. Each microservice can be independently secured and managed, allowing security measures to be applied selectively to only the active microservices rather than the entire monolithic application.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts only the necessary source code portions corresponding to active functional flows and compiles them into separate microservices. This extraction removes unnecessary code and reduces the attack surface by eliminating unexecuted code paths and reducing the overall codebase that could be exploited.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If source code is analyzed and refactored into microservices, then resource efficiency improves, but system complexity increases

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

Solution Approach 1:

The patent implements self-service through automated log analysis, functional flow identification, and source code discrimination. The system automatically analyzes service logs, identifies functional flows, extracts corresponding source code portions, and compiles microservices without requiring manual intervention, thereby managing the increased system complexity through automation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent uses feedback from service logs to drive the microservice refactoring process. By continuously analyzing operational logs to identify functional flows and using this feedback to guide source code discrimination and microservice compilation, the system adapts to actual service usage patterns, managing complexity through data-driven automation.

Inventive Principle:
Principle #23Feedback

4Ease of repair

If logs are analyzed and services are refactored dynamically, then serviceability improves, but processing time increases

Engineering Contradiction:
ImproveserviceabilityVSAvoidprocessing time
Core Design Contradiction:
Ease of repairVSLoss of time

Solution Approach 1:

The patent performs preliminary analysis of service logs and identification of functional flows before actual service issues occur. By pre-analyzing logs and pre-compiling microservices based on predicted functional flows, the system reduces processing time during incident response and improves serviceability through proactive rather than reactive approaches.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250103314A1Dynamic optimization of services
Publication Date: 2025.03.27 DELL PROD LP
  • US20250103314A1 patent drawing
  • US20250103314A1 patent drawing
  • US20250103314A1 patent drawing

AI summary

Methods and systems for managing operation of endpoint devices are disclosed. The operation of the endpoint devices may be managed by refactoring services into microservice based implementations. The service refactoring may be automated by monitoring functional flows of the service. The functional flows of the services may be captured in logs produced by the services. The functional flows may be used to identify portions of source code of the services corresponding to each of the functional flows. Microservices may be generated based on the identified portions of the source code.