Microservice Deployment Switching for Cost and Latency Balance

Solution Overview

Problem

Existing cloud-based microservices face inefficiencies and increased costs due to inflexible deployment strategies, where services are either run on dedicated nodes or serverless configurations without considering changing usage patterns or provider limitations, leading to potential performance issues and resource wastage.

Innovation Solution

A microservice deployment management system that dynamically adjusts deployment between dedicated nodes and serverless configurations based on monitored invocation rates and resource usage, automatically redeploying services as needed to optimize performance and cost-effectiveness.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If microservices are run on dedicated nodes 24×7, then service availability and performance are improved, but resource utilization efficiency deteriorates when invocation frequency is low

Engineering Contradiction:

Improveservice availabilityVSAvoidresource utilization efficiency

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements dynamic deployment configuration that automatically transitions microservices between dedicated node deployment and serverless deployment based on monitored invocation frequencies. This dynamic adjustment allows the system to optimize resource utilization while maintaining service availability by selecting the appropriate deployment mode according to actual usage patterns.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system changes the deployment parameter (deployment configuration) of microservices based on invocation frequency thresholds. When invocation frequency exceeds a threshold, the service is deployed on a dedicated node; when it falls below the threshold, the service is deployed serverlessly. This parameter change resolves the contradiction by adapting the deployment strategy to actual usage conditions.

Inventive Principle:

Principle #35Parameter changes

2Loss of energy

If microservices are deployed serverless, then resource cost is reduced for low-frequency services, but performance and response time deteriorate due to infrastructure setup overhead

Engineering Contradiction:

Improveresource costVSAvoidperformance response time

Core Design Contradiction:

Loss of energyVSSpeed

Solution Approach 1:

The patent implements dynamic deployment configuration that automatically transitions microservices between dedicated node deployment and serverless deployment based on monitored invocation frequencies. This dynamic adjustment allows the system to optimize resource utilization while maintaining service availability by selecting the appropriate deployment mode according to actual usage patterns.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system changes the deployment parameter (deployment configuration) of microservices based on invocation frequency thresholds. When invocation frequency exceeds a threshold, the service is deployed on a dedicated node; when it falls below the threshold, the service is deployed serverlessly. This parameter change resolves the contradiction by adapting the deployment strategy to actual usage conditions.

Inventive Principle:

Principle #35Parameter changes

3Ease of operation

If microservices are deployed serverless, then operational simplicity is improved, but reliability deteriorates due to provider limitations and execution interruptions

Engineering Contradiction:

Improveoperational simplicityVSAvoidservice reliability

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent implements dynamic deployment configuration that automatically transitions microservices between dedicated node deployment and serverless deployment based on monitored invocation frequencies. This dynamic adjustment allows the system to optimize resource utilization while maintaining service availability by selecting the appropriate deployment mode according to actual usage patterns.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system continuously monitors invocation frequencies of microservices and uses this feedback to automatically adjust deployment configurations. When invocation frequency exceeds a threshold indicating potential reliability issues with serverless deployment, the system transitions to dedicated node deployment. This feedback mechanism ensures service reliability while maintaining operational simplicity.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12530192B1Automatically determining and modifying environments for running microservices in a performant and cost-effective manner

Publication Date: 2026.01.20 CROWDSTRIKE

AI summary

Deployments of microservices executing in a cloud are automatically managed. Some microservices are deployed on dedicated nodes, others in serverless configurations. Rates of invocation and runtime data of microservices are monitored. Responsive to the monitored rate of invocation of a microservice running serverless exceeding a given threshold, the microservice is automatically redeployed to a dedicated node. A microservice executing on a dedicated node may be redeployed serverless if the infrequency with which it is called is sufficient. Microservices can be automatically redeployed between different dedicated nodes with different capacities based on monitored usage. The underlying cloud service provider may be automatically monitored for changes in serverless support functionality. Responsive to these changes, the thresholds at which microservices are redeployed can be automatically adjusted. Microservices may also be redeployed, and thresholds adjusted, in response to serverless microservice failures resulting from insufficient support provided by the underlying cloud service provider.