Configuration Microservice for Cloud Application Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a need for efficient and secure distribution of configuration information among disparate cloud applications developed using different cloud technologies and platforms, as conventional methods lack effective integration and consistency across independent applications.

Innovation Solution

A configuration microservice is introduced to store and manage configuration data in a generic format, allowing secure distribution and deployment across multiple microservices, ensuring integration and consistency by converting data to specific schemas as needed for each application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If configuration information is manually exchanged between independent cloud applications, then integration between applications is achieved, but the process is time-consuming and error-prone

Engineering Contradiction:
Improveintegration consistencyVSAvoidconfiguration distribution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces a configuration service as an intermediary component that mediates between applications and configuration data. This service receives configuration information from one application, validates it, and automatically distributes it to other applications that require it, eliminating manual exchange processes and ensuring consistency across the system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The configuration service performs preliminary validation and processing of configuration data before distribution. By pre-validating the configuration information against schemas and checking compatibility with target applications, the system prevents errors before they occur and reduces the time needed for configuration exchange.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If configuration data is distributed across multiple independent applications, then each application can use customized configuration information, but maintaining consistency and security becomes complex

Engineering Contradiction:
Improveconfiguration customizationVSAvoiddistribution management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The configuration service provides universal functionality for managing configuration data across different applications. It handles multiple operations including receiving, validating, storing, and distributing configuration information to various applications, reducing the need for separate management mechanisms in each application and simplifying overall system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system implements feedback mechanisms where the configuration service monitors the distribution status and validates configurations at each application. This feedback loop ensures consistency by detecting and reporting issues, allowing the service to maintain secure and consistent configuration distribution across multiple applications.

Inventive Principle:
Principle #23Feedback

3Reliability

If manual configuration exchange is used between applications, then security control is maintained, but the process is inefficient and prone to human error

Engineering Contradiction:
Improvesecurity controlVSAvoidconfiguration distribution efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The configuration service enables self-service configuration distribution where applications automatically request and receive configuration data from the service without manual intervention. The service autonomously validates, processes, and distributes configuration information while maintaining security controls, significantly improving efficiency while preserving reliability through automated security checks.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11252028B2Distribution of content in cloud applications
Publication Date: 2022.02.15 SAP SE
  • US11252028B2 patent drawing
  • US11252028B2 patent drawing
  • US11252028B2 patent drawing

AI summary

Systems and methods of a configuration distribution microservice include reception of a first data structure comprising first configuration data of a first type and associated with a first tenant of a first microservice, determination of one or more other microservices associated with the first tenant and the first type of configuration data, and transmission of an instruction to the determined one or more other microservices to deploy the first configuration data.