DATABASE TRIGGER-BASED EVENTING FOR DATA CHANGES BASED ON A PUBLISH/SUBSCRIBE MECHANISM
First Claim
1. A method comprising:
- receiving, at an event processor, a request from an application to subscribe to a database table event at an in-memory database;
storing, at the event processor, a subscription to the database table event;
sending, by the event processor, a subscription request to the in-memory database, wherein the subscription request indicates a subscription to the database table event;
handling, at the event processor, a notification, wherein the notification is received on behalf of the application in order to determine whether to publish the notification to an endpoint coupled to at least the application, wherein the notification indicates an identity of at least one database table at the in-memory database that has changed; and
publishing the notification to the endpoint.
1 Assignment
0 Petitions
Accused Products
Abstract
Methods and apparatus, including computer program products, are provided for handling database table changes. The method may include receiving, at an event processor, a request from an application to subscribe to a database table event at an in-memory database; storing, at the event processor, a subscription to the database table event; sending, by the event processor, a subscription request to the in-memory database, wherein the subscription request indicates a subscription to the database table event; handling, at the event processor, a notification, wherein the notification is received on behalf of the application in order to determine whether to publish the notification to an endpoint coupled to at least the application, wherein the notification indicates an identity of at least one database table at the in-memory database that has changed; and publishing the notification to the endpoint. Related systems, methods, and articles of manufacture are also disclosed.
-
Citations
20 Claims
-
1. A method comprising:
-
receiving, at an event processor, a request from an application to subscribe to a database table event at an in-memory database; storing, at the event processor, a subscription to the database table event; sending, by the event processor, a subscription request to the in-memory database, wherein the subscription request indicates a subscription to the database table event; handling, at the event processor, a notification, wherein the notification is received on behalf of the application in order to determine whether to publish the notification to an endpoint coupled to at least the application, wherein the notification indicates an identity of at least one database table at the in-memory database that has changed; and publishing the notification to the endpoint. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A system including at least one processor and at least one memory including program code which when executed causes operations comprising:
-
receiving, at an event processor, a request from an application to subscribe to a database table event at an in-memory database; storing, at the event processor, a subscription to the database table event; sending, by the event processor, a subscription request to the in-memory database, wherein the subscription request indicates a subscription to the database table event; handling, at the event processor, a notification, wherein the notification is received on behalf of the application in order to determine whether to publish the notification to an endpoint coupled to at least the application, wherein the notification indicates an identity of at least one database table at the in-memory database that has changed; and publishing the notification to the endpoint. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19)
-
-
20. A non-transitory computer-readable storage medium including program code which when executed causes operations comprising:
-
receiving, at an event processor, a request from an application to subscribe to a database table event at an in-memory database; storing, at the event processor, a subscription to the database table event; sending, by the event processor, a subscription request to the in-memory database, wherein the subscription request indicates a subscription to the database table event; handling, at the event processor, a notification, wherein the notification is received on behalf of the application in order to determine whether to publish the notification to an endpoint coupled to at least the application, wherein the notification indicates an identity of at least one database table at the in-memory database that has changed; and publishing the notification to the endpoint.
-
Specification