Configuration Handler Microservice for In-Memory Database Rollback

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Managing configuration profiles for cloud-based in-memory databases is challenging due to the need for efficient rollback of temporary changes across multiple instances, which increases time and resource requirements as the number of instances grows, and existing solutions lack efficient mechanisms for secure, scalable configuration handling.

Innovation Solution

A configuration handler microservice that receives requests to apply temporary changes to in-memory database configurations, adds a deprecation indication to the configuration profile, and restores the configuration to a previous state when the deprecation timestamp is exceeded, allowing for secure, scalable, and efficient management of configuration profiles across multiple instances.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If temporary configuration changes are applied to resolve defects in in-memory databases, then the database reliability is improved, but the complexity of managing configuration profiles increases

Engineering Contradiction:

Improvedatabase reliabilityVSAvoidconfiguration profile management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

A configuration handler microservice is introduced as an intermediary component that manages configuration profiles and their deprecation. This microservice receives configuration requests, adds deprecation indications to configuration profiles, and coordinates the rollback process, thereby reducing the operational complexity of managing temporary configuration changes across multiple database instances

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by automatically adding deprecation indications to configuration profiles when temporary changes are applied. This pre-marking enables automated tracking and future rollback operations, reducing the need for manual configuration management and improving reliability

Inventive Principle:

Principle #10Preliminary action

2Reliability

If configuration changes are applied to multiple in-memory database instances, then the defect resolution is improved, but the time required for rollback operations increases

Engineering Contradiction:

Improvedefect resolutionVSAvoidrollback operation time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The configuration handler microservice performs preliminary actions by automatically adding deprecation indications to configuration profiles at the time of temporary changes. This pre-marking stores metadata about which configurations need to be rolled back, enabling rapid automated rollback operations without manual intervention when the deprecation timestamp is exceeded

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the configuration handler continuously monitors configuration profiles and their deprecation timestamps. When the current time exceeds the deprecation timestamp, the system automatically triggers rollback operations, creating a closed-loop feedback system that ensures timely reversal of temporary changes

Inventive Principle:

Principle #23Feedback

3Ease of operation

If manual configuration management is used for multiple instances, then the ease of operation is maintained, but the productivity decreases due to increased time and resource requirements

Engineering Contradiction:

Improveconfiguration management easeVSAvoidconfiguration management efficiency

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The configuration handler microservice implements self-service functionality by automatically managing configuration profiles, adding deprecation indications, and executing rollback operations without requiring manual intervention. The system monitors its own state and autonomously performs configuration management tasks, improving productivity while maintaining ease of operation through automated workflows

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical configuration management processes with an automated software-based system. The configuration handler microservice uses software logic to manage configuration profiles, track deprecation timestamps, and execute rollbacks, substituting manual operations with automated computational processes that are faster and more efficient

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11550801B2Deprecating configuration profiles for cloud-based in-memory database

Publication Date: 2023.01.10 SAP SE

AI summary

A method for managing the configuration of an in-memory database running in a cluster of computing nodes may include receiving a configuration request to apply, to an instance of an in-memory database running on a cluster of computing nodes, one or more temporary changes to a configuration of the in-memory database. In response to the configuration request, an indication to deprecate the configuration profile may be added to a configuration profile associated with the instance of the in-memory database. The configuration profile may be deprecated based at least on the configuration profile being associated with the indication. The deprecating including restoring, to a state prior to the application of the one or more temporary changes, the configuration of the in-memory database. Related systems and articles of manufacture, including computer program products, are also provided.