Microservice Behavior Management via Request Context

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Microservice architectures face inefficiencies due to static resource allocation methods that fail to dynamically manage workloads, leading to resource shortages and overloads, resulting in penalized services and inefficient software application management.

Innovation Solution

A behavior management system that dynamically determines and executes service behavior configurations based on service type and identification data, using a behavior management catalog to exert fine-grained control over application behavior, allowing for efficient resource allocation and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If static resource allocation methods are used in microservice architectures, then device complexity is reduced and ease of operation is improved, but productivity deteriorates due to resource shortages and overloads

Engineering Contradiction:
Improveservice execution efficiencyVSAvoidbehavior management system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a behavior management system as an intermediary layer between service requests and service execution. This mediator dynamically determines service behavior configurations based on request context, enabling adaptive resource allocation without modifying the underlying microservice architecture. The behavior management system translates high-level service type data and service identification data into specific execution configurations, resolving the contradiction by adding intelligence where needed while keeping individual services simple.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent dynamically changes service execution parameters based on request context. Instead of static resource allocation, the system adjusts service behavior configurations (such as execution priority, resource allocation, routing decisions) in real-time based on service type data, service identification data, and current system state. This parameter adaptation enables productivity improvement without requiring complex permanent structural changes to the microservice architecture.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If static control over resource allocation is implemented, then device complexity is minimized, but adaptability deteriorates leading to penalized services during overload situations

Engineering Contradiction:
Improvedynamic service behavior controlVSAvoidresource allocation system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic service behavior control by continuously adapting service execution configurations based on current system conditions and request characteristics. The behavior management system determines different behavior configurations for different requests, enabling the system to respond dynamically to overload situations, service priorities, and resource availability. This dynamic approach improves adaptability while maintaining relatively simple device structure by using software-based configuration management rather than complex hardware control systems.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20240372924A1Application service behavior management using request context
Publication Date: 2024.11.07 SAP SE
  • US20240372924A1 patent drawing
  • US20240372924A1 patent drawing
  • US20240372924A1 patent drawing

AI summary

Techniques for managing application service behavior using request context are disclosed. In some embodiments, a computer system performs a method comprising: detecting a request sent by a service of an application, the service being one of a plurality of services included in a microservice architecture of the application, the request including a service type data that identifies the application and a service identification data that identifies the service; determining a behavior configuration for the request based on the service type data and the service identification data; and executing the service or another service of the plurality of services based on the determined behavior configuration.