Synchronous–Asynchronous Data Interface for Secure Cloud Scaling

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing local server systems face scalability constraints, maintenance overhead, geographic limitations, data protection compliance issues, security vulnerabilities, and latency problems in processing protected data, necessitating a transition to cloud computing environments for enhanced security and scalability.

Innovation Solution

A computer-implemented method and interface module facilitate the integration of synchronous batch-driven applications on local servers with asynchronous event-driven applications on cloud computing environments, utilizing conversion modules to transform data formats between the two systems, ensuring secure and efficient data processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If local servers are used for processing protected data, then data security and control are improved, but scalability and geographic accessibility deteriorate

Engineering Contradiction:

Improvedata securityVSAvoidscalability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

An interface module acts as an intermediary between local servers and cloud computing environments. This module enables secure data exchange by transforming data formats and protocols, allowing local servers to maintain security control while accessing cloud-based scalable resources. The interface module specifically handles authentication, encryption, and data format conversion to bridge the two systems.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is segmented into distinct components: local servers handling sensitive data processing, cloud computing environments providing scalable infrastructure, and interface modules managing communication. This segmentation allows each component to optimize for its specific function while maintaining overall system security and scalability.

Inventive Principle:

Principle #1Segmentation

2Reliability

If local servers are used for processing protected data, then data control is improved, but maintenance overhead and costs worsen

Engineering Contradiction:

Improvedata controlVSAvoidmaintenance overhead

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The interface module serves as a mediator that reduces maintenance overhead by automating data format transformation, protocol conversion, and system integration tasks. This eliminates the need for manual maintenance of complex integration logic and allows local servers to focus on core data processing functions.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The interface module implements self-service capabilities through automated authentication, encryption, and data transformation. The system automatically manages security protocols and data format conversions without requiring manual intervention, reducing maintenance burden on local servers.

Inventive Principle:

Principle #25Self-service

3Reliability

If synchronous batch-driven applications are used on local servers, then data processing reliability is improved, but processing speed and responsiveness deteriorate

Engineering Contradiction:

Improveprocessing reliabilityVSAvoidprocessing speed

Core Design Contradiction:

ReliabilityVSSpeed

Solution Approach 1:

Processing tasks are segmented between synchronous batch-driven applications on local servers (for reliable data processing) and asynchronous event-driven applications on cloud environments (for fast responsiveness). The interface module coordinates between these two processing modes, allowing each to operate in its optimal performance regime.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system dynamically switches between synchronous and asynchronous processing modes based on task requirements. Critical data processing operations use synchronous batch-driven approaches for reliability, while time-sensitive operations leverage asynchronous event-driven approaches for speed. The interface module manages this dynamic behavior.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS20250231823A1Interface for synchronous and asynchronous applications

Publication Date: 2025.07.17 BARCLAYS EXECUTION SERVICES LTD

AI summary

There is provided a computer-implemented method of interfacing one or more synchronous batch-driven applications running on a local server with one or more asynchronous event-driven applications running on a cloud computing environment. The method comprises first transformation steps and second transformation steps. The first transformation steps comprise receiving an event-driven message from a first asynchronous event-driven application, the event-driven message having a first data format type; transforming the event-driven message into a second data format type for a first synchronous batch-driven application; and transmitting the transformed event-driven message to the first synchronous batch-driven application. The second transformation steps comprise receiving a batch-driven message from a second synchronous batch-driven application, the batch-driven application having the second data format type; transforming the batch-driven message into the first data format type for a second asynchronous event-driven application; and transmitting the transformed batch-driven message to the second asynchronous event-driven application.