Unified Data Validation Architecture for Cloud Applications

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data validation methods in enterprise systems face challenges such as performance degradation due to round-trip communication between the frontend and backend, inconsistent data validation across different environments, and high development and maintenance costs due to separate validation procedures for backend and frontend systems.

Innovation Solution

A data validation procedure is developed in a first specification language, converted into different specification languages for backend and frontend environments, allowing for unified data validation across both systems without the need for round-trip processing, thereby ensuring consistent validation and reducing maintenance efforts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate data validation procedures are developed for backend and frontend systems, then data validation can be performed in both environments, but development and maintenance costs increase and consistency between environments deteriorates

Engineering Contradiction:

Improvedata validation consistencyVSAvoidvalidation procedure complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the backend and frontend validation procedures into a single unified validation procedure written in one specification language. This single procedure is then converted into both backend and frontend versions, eliminating the need to maintain separate validation logic and ensuring consistency across environments.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The unified validation procedure serves multiple functions by being converted into different specification languages for both backend and frontend systems. This single source validation procedure becomes universally applicable across different environments through automated conversion, reducing maintenance burden while maintaining reliability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If data validation is performed via round-trip communication between frontend and backend, then data integrity can be ensured, but system performance deteriorates due to additional network calls

Engineering Contradiction:

Improvedata integrityVSAvoidsystem performance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent performs data validation preliminarily on the frontend side using the converted frontend validation procedure before data is sent to the backend. This preliminary validation catches errors early, preventing unnecessary round-trip communications and improving system performance while maintaining data integrity through subsequent backend validation.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The unified validation procedure acts as an intermediary that generates both frontend and backend validation logic from a single source. This intermediary approach ensures that both frontend and backend use consistent validation rules, maintaining data integrity without requiring additional round-trip communication for validation coordination.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If separate validation procedures are maintained for backend and frontend, then each can be optimized for its specific environment, but maintenance effort and costs increase

Engineering Contradiction:

Improveenvironment-specific optimizationVSAvoiddevelopment and maintenance effort

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent segments the validation procedure into a unified source definition and environment-specific converted versions. The single specification language definition is segmented into backend and frontend implementations through automated conversion, allowing environment-specific optimization while reducing maintenance effort through centralized source management.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11036719B2Performance and quality optimized architecture for cloud applications

Publication Date: 2021.06.15 SAP SE

AI summary

A data validation procedure may be propagated to a server machine and to a client machine to perform the same data checking in the respective machines. The data validation procedure may be converted and expressed in a specification language that is suitable for the server machine. Likewise, the data validation procedure may be converted and expressed in a specification language that is suitable for the client machine.