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

• US 7,664,784 B2
• Filed: 01/11/2006
• Issued: 02/16/2010
• 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
• Primary Examiner(s): Lu; Kuen S
• Assistant Examiner(s): HO, BINH VAN
• Application Number:
  US11/330,431
• Publication Number:
  US 20070162511A1
• Time in Patent Office: 1,497 Days
• Field of Search: 707/200
• US Class Current: 1/1
• 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 method for publishing an event to a database, said method comprising:

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

examining an event repository for an event template associated with said event, said event repository communicatively coupled with said database and said messaging system;

retrieving said event template from said event repository;

marshalling said event template to create said event;

publishing said event in an event queue, said publishing including placing the event into the event queue;

removing said event from said event queue of said database in response to all subscribers expressing an interest in said event having consumed said event; and

removing from said event repository event templates having a number of requests that are below a defined threshold.

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

storing said event in said event repository once said event is removed from said event queue.

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

propagating said event to all subscribers of said database expressing an interest in said event.

4. The computer system as recited in claim 1 wherein said method further comprises:

reconstructing said event from said event template of said event when said event is located in said event repository.

5. The computer system as recited in claim 4 wherein said method further comprises:

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

6. A computer implemented method of publishing an event within a database system, said method comprising:

intercepting a request to publish a new event to the database for a subscriber, said request made by a publisher;

examining a plurality of stored events within an event repository to locate a stored event that matches said new event;

accessing said stored event from said event repository for use as a template in publishing said new event;

amending said template with values pertinent to said new event to create said new event;

placing said amended template into an event queue;

removing said amended template from said event queue in response to all subscribers expressing an interest in said new event having consumed said amended template; and

removing from said event repository stored events having a number of requests that are below a defined threshold.

7. The method as recited in claim 6 further comprising:

populating said event repository with additional events upon said additional events being de-queued from said event queue.

8. The method as recited in claim 6 wherein said plurality of stored events are organized within said event repository based on event type and event size.

9. The method as recited in claim 6 wherein said examining is performed predicated on said event type and said event size of said new event.

10. The method as recited in claim 6 further comprising:

removing select stored events from said event repository predicated on a frequency of matching associated with said select stored events being below a threshold frequency.

11. The method as recited in claim 6 further comprising:

propagating said new event to said subscriber.

12. A computer readable storage medium storing a plurality of instructions for controlling a processor to publish an event within a database system, the plurality of instructions comprising:

instructions for causing the processor to intercept a request to publish a new event to the database for a subscriber, said request made by a publisher;

instructions for causing the processor to examine a plurality of stored events within an event repository to locate a stored event that matches said new event;

instructions for causing the processor to access said stored event from said event repository for use as a template in publishing said new event;

instructions for causing the processor to amend said template with values pertinent to said new event to create said new event;

instructions for causing the processor to place said amended event into an event queue;

instructions for causing the processor to de-queue a given event in response to all subscribers that have expressed an interest in said given event having consumed said given event; and

instructions for causing the processor to remove from said event repository stored events having a number of requests that are below a defined threshold.

13. The computer readable storage medium of claim 12, further comprising instructions for causing the processor to populate said event repository with additional events upon said additional events being de-queued from said event queue.

14. The computer readable storage medium of claim 12, further comprising instructions for causing the processor to organize said plurality of stored events within said event repository based on event type and event size.

15. The computer readable storage medium of claim 14, wherein said instructions for causing the processor to examine the plurality of stored events include instructions for causing the processor to examine the plurality of stored events based on event type and event size.

16. The computer readable storage medium of claim 12, further comprising instructions for causing the processor to propagate said new event to said subscriber.

17. A computer readable storage medium storing a plurality of instructions for controlling a processor to publish an event within a database system, the plurality of instructions comprising:

instructions for causing the processor to intercept a request to publish a new event to the database for a subscriber, said request made by a publisher;

instructions for causing the processor to examine a plurality of stored events within an event repository to locate a stored event that matches said new event;

instructions for causing the processor to access said stored event from said event repository for use as a template in publishing said new event;

instructions for causing the processor to amend said template with values pertinent to said new event to create said new event;

instructions for causing the processor to place said amended event into an event queue;

instructions for causing the processor to remove said event from said event queue of said database in response to all subscribers expressing an interest in said event having consumed said event; and

instructions for causing the processor to remove from said event repository stored events having a number of requests that are below a defined threshold.