WebSocket Endpoint Database Update Trigger Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Web-based architectures fail to proactively notify client applications of database changes, leading to unnecessary load and network traffic due to polling mechanisms, and are limited by the request/response paradigm of HTTP, which prevents database updates from being provided without a pending client request.
Innovation Solution
A lightweight cross-session event mechanism using WebSocket protocol allows the application server to send updates to clients at any time, enabling full-duplex communications and extending database triggers to provide content updates to applications running on the server, thereby eliminating the need for frequent queries and reducing network traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If polling database content via periodically executed queries is used to notify client applications of changes, then client applications can be notified of database changes, but an unnecessary and possibly overwhelming load is introduced onto the database
Solution Approach 1:
The patent implements a push notification system where the database system actively sends feedback (change notifications) to client applications when data changes occur, eliminating the need for continuous polling. The database monitors changes and pushes updates to clients, creating a feedback loop that improves notification reliability while reducing database load.
Solution Approach 2:
The database system performs self-service by automatically detecting and notifying clients of changes without requiring client-initiated requests. The system maintains its own state information about data changes and proactively serves notification needs, reducing the burden on the database from continuous query processing.
2Device complexity
If all update traffic is provisioned through the application server, then update traffic can be managed centrally, but the application server must examine all incoming data traffic and does not account for applications connecting to the database via standard interfaces
Solution Approach 1:
The patent introduces a database trigger system that acts as an intermediary between database changes and client notifications. The trigger mechanism automatically handles update traffic and generates notifications without requiring the application server to examine all incoming data traffic, while still supporting applications connecting via standard interfaces like OData.
Solution Approach 2:
The solution provides universality by supporting multiple client connection methods (WebSocket for real-time, OData for standard interfaces) through a unified notification system. The database trigger system can serve both real-time push notification needs and standard interface requirements, enhancing adaptability.
3Ease of operation
If the request/response paradigm of HTTP is used, then client applications can request information from the server, but the server cannot proactively notify client applications of changes to database content
Solution Approach 1:
The patent transitions from the static request/response HTTP paradigm to a dynamic push notification system using WebSocket connections. This allows the server to dynamically initiate communication and send updates to clients at any time without waiting for client requests, reducing update delivery time while maintaining ease of operation through automated notification handling.
Data Source
AI summary
A system includes establishment of a WebSocket connection at a WebSocket endpoint of the system with a WebSocket client, registration of a callback at the WebSocket endpoint for an event associated with an update to data of the database, identification of an update to the data of the database at an HTTP endpoint of the system, sending, in response to the identification of the update, a trigger event from the HTTP endpoint, reception of the trigger event at the WebSocket endpoint, and execution of the callback by the WebSocket endpoint to transmit the update to the WebSocket client.