Volume Transaction Engine for Hybrid Cloud On-Premise Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing use of cloud applications in business enterprises has introduced complexity to transaction management, particularly in distributed or hybrid computing environments where on-premise and cloud-implemented applications need to communicate and coordinate effectively, making it difficult to set up and modify transaction processes.
Innovation Solution
A volume transaction engine is introduced to manage transactions across multiple computing systems by communicating with sales platform applications via an API. This engine executes process operations, coordinates with various backend systems, and handles communication between on-premise and cloud environments, facilitating transaction management in hybrid settings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If cloud applications are used to replace on-premise computing systems, then productivity and scalability are improved, but device complexity and difficulty of transaction management increase
Solution Approach 1:
The patent introduces a transaction engine as an intermediary component that sits between cloud applications and on-premise backend systems. This transaction engine abstracts the complexity of hybrid environment integration, providing a unified interface for transaction management while handling the coordination between cloud and on-premise systems internally.
Solution Approach 2:
The transaction engine is designed to perform multiple functions across different computing environments (cloud and on-premise). It can execute transactions, coordinate between systems, manage data flow, and adapt to different backend configurations, making it a universal solution that reduces overall system complexity despite the heterogeneous environment.
2Adaptability or versatility
If hybrid computing environments are implemented to use both on-premise and cloud systems, then adaptability and versatility are improved, but ease of operation and modification of transaction processes deteriorate
Solution Approach 1:
The transaction engine serves as a mediator that shields operators from the underlying complexity of hybrid environments. It provides a standardized interface and abstraction layer, allowing transaction processes to be configured and modified through unified mechanisms rather than dealing with separate cloud and on-premise system configurations.
Solution Approach 2:
The system segments transaction management into distinct layers: the transaction engine handles environment-specific complexities internally, while presenting a simplified, unified interface to operators. This segmentation allows the complex hybrid environment support to be isolated within the engine without affecting the ease of operation at the user level.
Data Source
AI summary
Various examples are directed to systems and methods for executing transactions in a hybrid computing environment. A volume transaction engine may receive first transaction request data from a first transaction platform application and select transaction description data describing a plurality of process operations for executing the first transaction. The volume transaction engine may execute the first process operation at least in part by accessing a first backend system executing at the cloud platform deployment and execute a second process operation at least in part by accessing a second backend system executed by an on-premise computing system.