Database Connectivity Adapter for Event Processing Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing event processing systems lack a standard Application Programming Interface (API) for communication between client applications and event processing servers, leading to proprietary interfaces that complicate interoperability and compatibility with different server implementations and legacy applications.
Innovation Solution
A framework utilizing a standard database connectivity API, such as Java Database Connectivity (JDBC), facilitates communication between client applications and event processing servers through a database connectivity adapter that processes query language statements and invokes appropriate procedures within the event processing server, enabling intra-process communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a proprietary interface is used for client application to event processing server communication, then the server can provide customized functionality, but client applications cannot easily migrate or interoperate with different server implementations
Solution Approach 1:
The patent introduces a database connectivity adapter as an intermediary layer between the client application and the event processing server. This adapter implements standard database connectivity APIs (such as JDBC) and translates client queries into event processing server-specific operations, enabling interoperability without requiring custom code in client applications.
Solution Approach 2:
The event processing server is designed to support multiple communication protocols and interfaces, including standard database connectivity APIs and proprietary interfaces. This universality allows the server to serve diverse client applications with different requirements while maintaining a unified processing architecture.
2Reliability
If a proprietary interface is used, then the server can be optimized for specific workloads, but legacy client applications cannot interact with the server
Solution Approach 1:
The database connectivity adapter serves as a bridge between legacy client applications using standard database APIs and the event processing server. It receives standard SQL queries from legacy applications, translates them into event processing server commands, and returns results in the expected format, ensuring compatibility without modifying legacy applications.
3Ease of operation
If custom code is required for each client application, then the interface can be highly customized, but development time and complexity increase
Solution Approach 1:
The system enables client applications to interact with the event processing server using standard database connectivity APIs that they already know and use, without requiring custom integration code. The adapter handles the translation and communication protocols automatically, allowing applications to serve themselves through familiar interfaces.
Data Source
AI summary
Techniques for facilitating communication between one or more client applications and an event processing server. In one set of embodiments, a framework is provided that enables a client application to communicate with an event processing server via a standard database connectivity API, such as Java Database Connectivity (JDBC).