High-performance, scalable, adaptive and multi-dimensional event repository

• US 8,631,024 B2
• Filed: 12/29/2009
• Issued: 01/14/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: Venkatesan, Ramkumar, Lakshminath, Anand
• Primary Examiner(s): HO, BINH VAN
• Application Number:
  US12/649,209
• Publication Number:
  US 20100169350A1
• Time in Patent Office: 1,477 Days
• Field of Search: 707/756
• US Class Current: 707/758
• 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 marshalling 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 for utilizing an event repository, the method comprising:

receiving, by a processor of a computer system, an indication that all subscribers of a database expressing interest in an event have consumed the event;

removing the event from an event queue in response to receiving the indication;

placing the event in an event repository upon removal of the event from the event queue, the event stored in the event repository to facilitate publication of a subsequent event similar to the event, the subsequent event corresponding to a change in the database;

updating values of the template with values pertinent to the subsequent event;

publishing the subsequent event in the event queue; and

adjusting the number of the events retained in the event repository predicated at least on memory usage thereof and frequency of matching for individual events.

2. The method as recited in claim 1 further comprising:

intercepting a request to publish the subsequent event, said intercepting performed by a messaging system operable in conjunction with said database.

3. The method as recited in claim 2 further comprising:

examining the event repository for a match to the subsequent event upon said intercepting.

4. The method as recited in claim 1 further comprising:

reconstructing the subsequent event from a template of the event in response to a match of the event in the event repository.

5. The method as recited in claim 1 further comprising:

propagating the subsequent event to all database subscribers expressing interest in the event.

6. A non-transitory computer-readable storage medium having stored thereon instructions causing at least one computer system to utilize an event repository, the instructions comprising:

instructions that cause said at least one computer system to receive an indication that all subscribers of a database expressing interest in an event have consumed the event;

instructions that cause said at least one computer system to remove the event from an event queue in response to receiving the indication;

instructions that cause said at least one computer system to place the event in an event repository upon removal of the event from the event queue, the event stored in the event repository to facilitate publication of a subsequent event similar to the event, the subsequent event corresponding to a change in the database;

instructions that cause said at least one computer system to update values of the template with values pertinent to the subsequent event;

instructions that cause said at least one computer system to publish the subsequent event in the event queue; and

instructions that cause said at least one computer system to adjust the number of the events retained in the event repository predicated on memory usage thereof and predicated on frequency of matching for individual events.

7. The non-transitory computer-readable storage medium as recited in claim 6 further comprising:

instructions that cause said at least one computer system to intercept a request to publish the subsequent event, said interception performed by a messaging system operable in conjunction with the database.

8. The non-transitory computer-readable storage medium as recited in claim 7 further comprising:

instructions that cause said at least one computer system to examine the event repository for a match to the subsequent event upon said interception.

9. The non-transitory computer-readable storage medium as recited in claim 6 further comprising:

instructions that cause said at least one computer system to reconstruct the subsequent event from a template of the event in response to a match of the event in the event repository.

10. The non-transitory computer-readable storage medium as recited in claim 6 further comprising:

instructions that cause said at least one computer system to propagate the subsequent event to all database subscribers expressing interest in the event.

11. A system for utilizing an event repository, comprising:

at least one or more computer systems having one or more processors;

a database;

a messaging system having an event queue and operable with the database to;

store the events of the database in an event queue;

receive an indication that all subscribers of the database expressing interest in an event have consumed the event;

remove the event from the event queue in response to receiving the indication;

place the event in an event repository upon removal of the event from the event queue, the event stored in the event repository to facilitate publication of a subsequent event similar to the event, the subsequent event corresponding to a change in the database;

wherein the messaging system is further operable to update values of the template with values pertinent to the subsequent event and publish the subsequent event in the event queue; and

wherein the messaging system is further operable to adjust the number of the events retained in the event repository predicated at least on memory usage thereof and frequency of matching for individual events.

12. The system of claim 11, wherein the messaging system is further operable to intercept a request to publish the subsequent event.

13. The system of claim 12, wherein the messaging system is further operable to examine the event repository for a match to the subsequent upon intercepting the subsequent event.

14. The system of claim 11, wherein the messaging system is further operable to reconstruct the subsequent event from a template of the event in response to a match of the event in the event repository.