Centralized Controller for Cloud Database Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of database systems makes deployment, development, and configuration in cloud services difficult due to configuration differences between instances, leading to errors and reduced consistency and reproducibility.

Innovation Solution

A centralized controller uses database views to create a union view of data from multiple database tables, performing calculations to update configuration metadata and manage settings such as memory allocation, bandwidth, and processor capacity across database instances hosted on cloud services, utilizing the OData protocol for data retrieval and updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple database instances are deployed in cloud services with different configurations, then adaptability and versatility are improved, but device complexity and difficulty of deployment increase

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoiddatabase system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A centralized controller is introduced as an intermediary component that manages configuration data for multiple database instances. The controller retrieves configuration data from a shared database, performs calculations to determine actual configuration values, and pushes these values to individual database instances. This mediator simplifies the complexity of managing multiple instances with different configurations by centralizing the management function.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If configuration data is stored in multiple database tables at cloud services, then adaptability is improved, but ease of operation and consistency reduce

Engineering Contradiction:
Improveconfiguration customizationVSAvoidconfiguration management ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

Multiple database tables storing configuration data for different database instances are merged into a single shared database table at the centralized controller. This consolidation allows the controller to retrieve all configuration data through a single query, perform unified calculations, and maintain consistency across all instances. The merging operation simplifies configuration management by eliminating the need to access and update multiple separate tables.

Inventive Principle:
Principle #5Merging (Combining)

3Ease of operation

If database views are used to retrieve data from multiple tables, then ease of operation is improved, but device complexity increases

Engineering Contradiction:
Improvedata retrieval easeVSAvoiddatabase view complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

Database views are pre-configured to define the structure and relationships between multiple database tables before data retrieval operations are performed. These pre-defined views simplify the data retrieval process by providing a standardized interface that the centralized controller can query without needing to manually construct complex join operations. The preliminary creation of views abstracts the complexity of multi-table relationships.

Inventive Principle:
Principle #10Preliminary action

4Manufacturing precision

If configuration metadata is updated through calculation views, then manufacturing precision and consistency are improved, but productivity and update speed decrease

Engineering Contradiction:
Improveconfiguration consistencyVSAvoidconfiguration update speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system implements a feedback mechanism where the centralized controller retrieves configuration data, performs calculations to determine actual values, and pushes updated values back to database instances. This feedback loop ensures consistency by verifying and validating configuration values before applying them. The feedback mechanism allows for error checking and validation that maintains precision while managing update speeds through efficient data processing at the controller.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11841840B2Technical system settings using a shared database
Publication Date: 2023.12.12 SAP SE
  • US11841840B2 patent drawing
  • US11841840B2 patent drawing
  • US11841840B2 patent drawing

AI summary

In some implementations, there is provided a method including receiving, by a centralized controller, data from a plurality of database tables at a plurality of database instances at a cloud service, wherein the data is received via a plurality of database views on the plurality of database tables; in response to receiving the data, performing, by the centralized controller, a union view of the data obtained from the plurality of database views; storing, by the centralized controller, the union view of the data as configuration metadata; and performing, by the centralized controller, at least one calculation view to update a value of the configuration metadata and to provide the updated value to at least one of the plurality of database tables at the cloud service. Related systems and articles of manufacture are also disclosed.