HIGH-PERFORMANCE, SCALABLE, ADAPTIVE AND MULTI-DIMENSIONAL EVENT REPOSITORY

• US 20140129515A1
• Filed: 01/13/2014
• Published: 05/08/2014
• Est. Priority Date: 01/11/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Lakshminath, Anand, Venkatesan, Ramkumar
• Granted Patent: US 9,063,961 B2
• Time in Patent Office: Days
• US Class Current: 707/609
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

A High-Performance, Scalable, Adaptive and Multi-dimensional Event Repository is described and utilized in a method for publishing an event in a database. The present method includes transparently intercepting a request to a database to publish an event. A messaging system operable with the database intercepts the request. The present method further includes examining an event repository for a template of the event. The event repository is operable with the database and the messaging system. The present method additionally includes retrieving the event template from the event repository. The present method also includes marshaling the event template to create the event. The present method also includes publishing the event in an event queue.

Claims

1. A computer-implemented method, comprising:

intercepting, by a computer system, a request to publish an event to a database, the intercepting performed by a messaging system operable with the database;

examining, by the computer system, an event repository for an event template associated with the event, the examining performed by the messaging system, the event repository communicatively coupled with the database and the messaging system;

retrieving the event template from the event repository;

marshaling the event template to create the event; and

publishing the event in an event queue.

2. The method of claim 1, further comprising removing the event from the event queue of the database in response to a subscriber expressing an interest in the event having consumed the event.

3. The method of claim 2, further comprising storing the event in the event repository once the event is removed from the event queue.

4. The method of claim 1, further comprising propagating the event to a subscriber of the database expressing an interest in the event.

5. The method of claim 1, further comprising removing event templates from the event repository having requests that are below a threshold.

6. The method of claim 1, further comprising reconstructing the event from the template of the event when the event is located in the event repository.

7. The method of claim 6, further comprising updating values associated with the event upon reconstruction of the event.

8. A system, comprising:

a memory configured to store computer-executable instructions; and

a processor configured to access the memory and execute the computer-executable instructions to at least;

intercept a request to publish an event to a database, the intercepting performed by a messaging system operable with the database;

examine an event repository for an event template associated with the event, the examining performed by the messaging system, the event repository communicatively coupled with the database and the messaging system;

retrieve the event template from the event repository;

marshal the event template to create the event; and

publish the event in an event queue.

9. The system of claim 8, wherein the processor is further configured to execute the computer-executable instructions to at least remove the event from the event queue of the database in response to a subscriber expressing an interest in the event having consumed the event.

10. The system of claim 9, wherein the processor is further configured to execute the computer-executable instructions to at least store the event in the event repository once the event is removed from the event queue.

11. The system of claim 8, wherein the processor is further configured to execute the computer-executable instructions to at least propagate the event to a subscriber of the database expressing an interest in the event.

12. The system of claim 8, wherein the processor is further configured to execute the computer-executable instructions to at least remove event templates from the event repository having requests that are below a threshold.

13. The system of claim 8, wherein the processor is further configured to execute the computer-executable instructions to at least reconstruct the event from the template of the event when the event is located in the event repository.

14. The system of claim 13, wherein the processor is further configured to execute the computer-executable instructions to at least update values associated with the event upon reconstruction of the event.

15. A non-transitory computer-readable storage medium configured with computer-executable instructions that, when executed by a computer system, cause the computer system to perform operations comprising:

intercepting, by a computer system, a request to publish an event to a database, the intercepting performed by a messaging system operable with the database;

examining, by the computer system, an event repository for an event template associated with the event, the examining performed by the messaging system, the event repository communicatively coupled with the database and the messaging system;

retrieving the event template from the event repository;

marshaling the event template to create the event; and

publishing the event in an event queue.

16. The non-transitory computer-readable storage medium of claim 15, further comprising removing the event from the event queue of the database in response to a subscriber expressing an interest in the event having consumed the event.

17. The non-transitory computer-readable storage medium of claim 16, further comprising storing the event in the event repository once the event is removed from the event queue.

18. The non-transitory computer-readable storage medium of claim 15, further comprising propagating the event to a subscriber of the database expressing an interest in the event.

19. The non-transitory computer-readable storage medium of claim 15, further comprising removing event templates from the event repository having requests that are below a threshold.

20. The non-transitory computer-readable storage medium of claim 15, further comprising:

reconstructing the event from the template of the event when the event is located in the event repository; and

updating values associated with the event upon reconstruction of the event.