ABAP Cloud Functions WebSocket Bidirectional Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud-based DevOps solutions are language-specific and do not support Advanced Business Application Programming (ABAP), limiting their applicability to On-Premise and in-memory database deployments, and are not extendible to cloud-like development and monitoring functionalities.
Innovation Solution
Implementing ABAP Cloud Functions that utilize WebSockets for bidirectional communication, enabling the development of event-based cloud functions and extending support to On-Premise and in-memory database deployments, with a push channel protocol for efficient message transmission and integration with existing ABAP-based applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If cloud-based DevOps solutions use language-specific implementations (JavaScript, Java, C#, F#), then development efficiency and tooling support are improved, but language versatility and support for ABAP are lost
Solution Approach 1:
The patent implements a universal cloud function platform that supports multiple programming languages including ABAP, JavaScript, Java, C#, and F#. The system provides a common development environment, deployment mechanism, and runtime infrastructure that can execute functions written in different languages, thereby achieving language versatility while maintaining cloud-based DevOps capabilities.
Solution Approach 2:
The patent introduces an intermediary layer (the cloud function platform) that sits between the diverse programming languages and the underlying infrastructure. This intermediary provides language-agnostic abstractions for event handling, resource management, and deployment, allowing ABAP and other languages to utilize cloud capabilities without requiring language-specific cloud implementations.
2Ease of operation
If cloud functions are implemented with PaaS architecture, then ease of deployment and management are improved, but extendibility to On-Premise and in-memory database deployments is limited
Solution Approach 1:
The patent implements a dynamic deployment architecture that can adapt to different deployment environments (cloud PaaS, On-Premise, in-memory databases). The system allows configuration and adaptation of the cloud function runtime based on the target environment, enabling the same ABAP code to be deployed across diverse platforms without requiring separate implementation approaches.
Solution Approach 2:
The cloud function platform is designed to provide universal support for multiple deployment scenarios. It maintains core PaaS capabilities (automatic scaling, event-driven architecture, resource management) while extending functionality to support On-Premise deployments and in-memory database integrations, making the system versatile across different operational contexts.
3Speed
If ABAP Cloud Functions are implemented with WebSocket bidirectional communication, then real-time event processing capability is improved, but communication protocol complexity increases
Solution Approach 1:
The patent introduces WebSocket technology as an intermediary communication mechanism between ABAP Cloud Functions and event sources. The WebSocket protocol handles the complexity of bidirectional real-time communication, while the ABAP function code interacts with simplified event handling interfaces. This mediator approach enables real-time processing without requiring ABAP developers to directly manage complex communication protocols.
Data Source
AI summary
In an example, a WebSocket is used as an abstraction layer on top of one or more triggers. These triggers may be defined by DevOps tools and may be called bidirectionally. Specifically, a web application can call a trigger located in a Function as a Service layer at an ABAP application server, while the ABAP application server can also push data via a push channel through the WebSocket to trigger functions in the Web App.