Behavior Toggle for Stateful Cloud Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face difficulties in utilizing new software or features due to lack of context-aware guidance, leading to frustration and abandonment, as existing solutions rely on non-context aware product support like bots that lack necessary context.

Innovation Solution

Implementing a behavior toggle for stateful applications in cloud environments, which once enabled, cannot be disabled without explicit migration, and is integrated with Kubernetes to manage the lifecycle of stateful applications, providing context-aware support by specifying behavior versions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If behavior toggle is enabled for stateful applications, then user experience and consistency are improved, but system complexity increases

Engineering Contradiction:
Improvebehavior consistencyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a behavior toggle as an intermediary mechanism that mediates between different application versions and user behaviors. The behavior toggle stores version information and behavior flags that act as a mediator to ensure consistent behavior across application updates without requiring complex coordination between components.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The behavior toggle is configured in advance with specific behavior versions and flags before application execution. This preliminary configuration ensures that when applications run, they automatically adhere to the predefined behavior version, eliminating the need for runtime negotiations or complex version detection mechanisms.

Inventive Principle:
Principle #10Preliminary action

2Stability of the object's composition

If behavior toggle prevents disabling without migration, then application stability is improved, but ease of operation deteriorates

Engineering Contradiction:
Improveapplication stabilityVSAvoidconfiguration flexibility
Core Design Contradiction:
Stability of the object's compositionVSEase of operation

Solution Approach 1:

The behavior toggle system dynamically adapts its constraints based on the application state. While the toggle prevents arbitrary disabling to maintain stability, it provides structured migration paths that allow controlled changes when needed. The system transitions from a static configuration to a dynamic one that responds to migration events.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system manages configuration flexibility through parameter changes in the behavior toggle settings. When migration is required, the system changes the behavior version parameter in a controlled manner, allowing the application to adapt to new behaviors while maintaining stability through the structured parameter transition process.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If context-aware support is implemented, then user frustration is reduced, but device complexity increases

Engineering Contradiction:
Improveuser experienceVSAvoidsupport system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The behavior toggle enables the application to self-configure based on stored behavior versions and flags. Instead of requiring complex external support systems to analyze user context and provide guidance, the application automatically adapts its behavior based on the toggle settings, providing context-aware support through self-service mechanisms.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Context information is pre-configured in the behavior toggle during application deployment or initial setup. This preliminary action stores the necessary context data that the application can automatically retrieve and use to adjust its behavior, eliminating the need for complex real-time context analysis systems.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12135982B2Behavior toggle for stateful applications
Publication Date: 2024.11.05 SAP SE
  • US12135982B2 patent drawing
  • US12135982B2 patent drawing
  • US12135982B2 patent drawing

AI summary

In an example embodiment, a specialized software object, called a behavior toggle, is utilized for stateful applications in cloud environments. The behavior toggle, once enabled and used by an entity, is not able to be disabled anymore for that entity, other than by explicit migration. Unlike feature toggles, whose values are expressed using “true” or “false” flags or the like, behavior toggles are enabled by specific version. Specifically, the value indicates which version of the behavior is enabled. The behavior toggle software objects may then be referenced by, or included in, other software objects, to utilize the behavior toggle software objects with the other software objects and have the behavior toggle be applied to the other software objects.