Serverless Microservice Cold-Start Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Serverless microservices experience significant cold-start latency due to the time it takes for containers to scale from zero instances to handle incoming requests, leading to increased response times and resource waste in microservice-based applications.

Innovation Solution

A method that proactively scales selected microservices from zero instances based on predefined rules applied to incoming requests or events, ensuring that only necessary microservices are activated, reducing the cumulative cold-start time and resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If serverless microservices are deployed to reduce infrastructure complexity, then device complexity is reduced, but cold-start latency increases

Engineering Contradiction:
Improveinfrastructure complexityVSAvoidcold-start latency
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by proactively scaling selected microservices from zero instances before incoming requests arrive. The system predicts future request patterns and pre-activates microservices in advance, so when requests actually come in, the microservices are already ready to handle them, eliminating cold-start latency while maintaining serverless infrastructure simplicity

Inventive Principle:
Principle #10Preliminary action

2Reliability

If all microservices are scaled up to handle requests, then reliability is improved, but resource waste increases

Engineering Contradiction:
Improverequest handling capabilityVSAvoidresource waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies segmentation by dividing microservices into different categories based on their importance and request patterns. The system identifies critical microservices that should be proactively scaled versus non-critical ones that can wait. This selective segmentation allows the system to scale only the necessary microservices, improving request handling reliability for essential services while reducing resource waste for less critical ones

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by predicting which microservices will be needed based on request patterns and proactively scaling only those selected microservices before requests arrive. This prevents scaling unnecessary microservices while ensuring critical ones are ready, thereby improving reliability for essential services and reducing resource waste overall

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If microservices are scaled from zero instances, then adaptability is improved, but start latency increases

Engineering Contradiction:
Improvescaling capabilityVSAvoidservice startup speed
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The patent applies preliminary action by proactively scaling selected microservices from zero instances before incoming requests arrive. The system predicts future request patterns and pre-activates microservices in advance, so when requests actually come in, the microservices are already ready to handle them, eliminating cold-start latency while maintaining serverless infrastructure simplicity

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20220253347A1Reducing start latency of serverless microservices
Publication Date: 2022.08.11 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US20220253347A1 patent drawing
  • US20220253347A1 patent drawing
  • US20220253347A1 patent drawing

AI summary

A process or may reduce start latency of serverless microservices. The processor may detect an incoming request or event to an application in a serverless microservice environment. The incoming request or event may initiate a chain of invocations of one or more microservices of the application. The processor may select an amount of selected microservices from the one or more microservices of the application. The amount of selected microservices may perform a task of the incoming request or event. The task may apply one or more predefined application-specific rules to one or more elements of the incoming request or event to determine the amount of selected microservices. The processor may trigger scaling up activation of the one or more microservices of the application. The processor may invoke the one or more microservices of the application to match the amount of selected microservices.