Serverless Transaction Adapter for Multi-Platform Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud computing platforms often lack native transaction solutions for clients, requiring clients to build integrations with various transaction gateways and deal with proprietary programming languages, leading to time-consuming and costly implementations, especially for payment processing.
Innovation Solution
A transaction system with a serverless architecture that provides multi-language, multi-platform support, allowing vendors to develop and deploy serverless functions in any programming language, enabling seamless integration with cloud computing platforms like Salesforce.com, without the need for proprietary language expertise.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If clients build integrations with various transaction gateways using proprietary programming languages, then transaction processing capability is achieved, but implementation time and costs increase significantly
Solution Approach 1:
The patent introduces an intermediary layer (adapter pattern) between the cloud computing platform and various transaction gateways. This adapter layer provides standardized interfaces that translate between different gateway protocols and the platform's native language, eliminating the need for clients to directly integrate with each gateway using proprietary languages.
Solution Approach 2:
The patent creates a universal transaction processing framework that can handle multiple transaction gateways and types through a common interface. The adapter layer is designed to be language-agnostic and gateway-agnostic, allowing the same platform to support diverse transaction processors without requiring separate integration code for each.
2Reliability
If clients build integrations with various transaction gateways using proprietary programming languages, then transaction processing capability is achieved, but implementation costs increase significantly
Solution Approach 1:
The adapter layer serves as a cost-effective intermediary that centralizes integration logic. Instead of paying for multiple specialized integrations, clients pay once for the adapter framework that handles all gateway translations, significantly reducing implementation costs.
Solution Approach 2:
The patent changes the parameter of programming language requirements from proprietary to standard languages. By allowing adapters to be written in standard languages (Java, Python, etc.) rather than requiring platform-specific proprietary languages, the solution reduces dependency costs and makes the system more economically viable.
3Ease of operation
If cloud computing platforms provide native transaction solutions, then transaction processing becomes simpler, but platform complexity and development costs increase
Solution Approach 1:
The adapter layer acts as an intermediary that absorbs platform complexity while presenting simplicity to clients. The complex gateway-specific logic is isolated in the adapter layer, which the platform maintains and updates, while clients interact only with the simple, standardized interface.
Solution Approach 2:
The patent segments the system into distinct layers: the client layer (simple), the adapter layer (complex), and the gateway layer (varied). This segmentation allows the platform to provide simple transaction processing to clients while containing complexity in the intermediate adapter layer that the platform controls.
Data Source
AI summary
Technologies are provided for a cloud computing platform (CCP) to request a transaction via a third-party vendor and receive a transaction response result of that transaction from another cloud computing platform having a serverless capability such that at least part of the transaction occurs at the other cloud computing platform. A transaction request having a specific transaction type (TT) is sent to an adapter, which sends another call with the transaction request to the public cloud. The specific TT corresponds to a particular serverless function (SF) of the third-party vendor. A particular template t corresponds to the specific TT. The particular template is a code statement that follows a standard code definition written in the proprietary programming language of the CCP. The other cloud computing platform invokes the particular SF to generate a transaction response that is consumable by the CCP.