Common Format Process for Multi-Protocol Cloud Database Requests

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Enterprise database systems face challenges when custom application logic code is integrated directly, as it complicates upgrades and requires frequent updates to maintain compatibility, and supporting multiple programming languages for interfaces increases costs and reduces efficiency.

Innovation Solution

Implementing a common format process that translates requests between various protocols, allowing application logic code in different programming languages to interact with the enterprise database system through a microservice architecture, reducing the need for frequent updates and minimizing the cost of developing multiple interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom application logic code is integrated directly into the enterprise database system, then the system can execute enterprise-specific requirements and processes, but it complicates upgrades and requires frequent updates to maintain compatibility

Engineering Contradiction:

ImproveAbility to execute enterprise-specific requirementsVSAvoidComplexity of system integration

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments application logic into separate deployable units (microservices or plugins) that can be independently managed, updated, and deployed without affecting the core database system. This allows enterprise-specific logic to be executed while maintaining system upgradeability and reducing integration complexity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

An intermediary layer or adapter pattern is introduced between the enterprise database system and custom application logic. This mediator handles protocol translations and interface standardizations, allowing custom logic to be executed while isolating the core system from direct integration complications.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple programming languages are supported for interfaces, then the system can accommodate diverse application logic codes, but it increases costs and reduces efficiency

Engineering Contradiction:

ImproveSupport for multiple programming languagesVSAvoidDevelopment efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system implements a universal interface layer or common protocol that can handle multiple programming languages and communication formats. This universal interface translates diverse incoming requests into a standardized internal format, enabling multi-language support while maintaining development efficiency through code reuse and standardized processing paths.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS12001395B2Request handling in a multi-protocol cloud environment

Publication Date: 2024.06.04 SAP SE

AI summary

Various examples are directed to systems and methods for operating an application for use with an enterprise database system. A common format process may receive, from a user device, a first request directed to the enterprise database system, convert the first request into a common protocol, and send a first common protocol request to the application logic code. The application logic code may generate a second request in the common protocol and send the second request to the common format process. The common format process may convert the second request from the common protocol to a database query protocol to generate at least one database query and send the at least one database query to the enterprise database system.