Dynamic Service Instance Management for Resource Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional monolithic application procedures consume excessive computing resources due to the need for horizontal extension to meet service requests, leading to inefficient resource utilization.

Innovation Solution

A program generation system and service system that parse and embed methods into communication interface function codes, allowing for dynamic instance management, routing, and extension control to optimize resource allocation by generating and managing instances based on demand.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If horizontal extension of monolithic application procedures is used to meet service requests, then service capacity is improved, but computing resource consumption increases excessively

Engineering Contradiction:
Improveservice capacityVSAvoidcomputing resource consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent segments the monolithic application procedure into multiple independent microservices (first service procedure, second service procedure, third service procedure). Each microservice handles specific business logic independently, allowing the system to scale selectively and efficiently without deploying entire monolithic applications, thereby reducing computing resource consumption while maintaining service capacity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic instance management where the number of service instances is adjusted based on actual demand. The system dynamically creates, suspends, or removes service instances (first service instance, second service instance, third service instance) according to request patterns, enabling flexible resource allocation that matches actual workload and avoids excessive resource consumption.

Inventive Principle:
Principle #15Dynamics

2Reliability

If multiple service instances are created to handle requests, then service availability is improved, but device complexity increases

Engineering Contradiction:
Improveservice availabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the management of multiple service instances under a unified service management mechanism. The system consolidates instance creation, suspension, and removal operations into a coordinated framework that handles first, second, and third service instances through standardized procedures, reducing operational complexity despite having multiple instances for improved availability.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements feedback-based instance management where the system monitors service requests and automatically adjusts the number and state of service instances accordingly. When service requests are detected, the system activates appropriate instances; when requests subside, instances are suspended or removed. This closed-loop control maintains service availability while preventing unnecessary complexity through automated, demand-driven management.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250023783A1Program generation system, program generation method, service system, and service system execution method
Publication Date: 2025.01.16 XINCHEN FINTECH CO LTD
  • US20250023783A1 patent drawing
  • US20250023783A1 patent drawing
  • US20250023783A1 patent drawing

AI summary

A service system execution method is applicable to a service system and includes: calling a plurality of methods sequentially by a control unit based on an external request; generating and running an instance by a service unit based on a first indication and closing the aforementioned instance based on a second indication; receiving call parameters of a current method by a routing unit and executing: recording a request and the call parameters of the current method in response to a number of instances corresponding to the current method being zero; and selecting a service instance from the running instances corresponding to the current method based on a selection procedure in response to the number of instances corresponding to the current method being non-zero; and controlling a survival status of all the instances and executing an extension procedure at predetermined intervals by an extension control unit.