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

• US 20070162511A1
• Filed: 01/11/2006
• Published: 07/12/2007
• 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 7,664,784 B2
• Time in Patent Office: Days
• 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 in a database, said method comprising:

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

examining an event repository for an event template associated with said event, said examining performed by said messaging system, 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; and

publishing said event in an event queue.

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

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.

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

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

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

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

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

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

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

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

7. The computer system as recited in claim 6 wherein said method further comprises:

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

8. A method for utilizing an event repository, said method comprising:

receiving an indication that all subscribers of a database expressing interest in an event have consumed said event;

removing said event from an event queue in response to receiving said indication; and

placing said event in an event repository upon removal of said event from said event queue, said event stored in said event repository to facilitate publication of a subsequent event similar to said event.

9. The method as recited in claim 8 further comprising:

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

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

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

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

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

12. The method as recited in claim 8 further comprising:

updating values of said template with values pertinent to said subsequent event; and

publishing said subsequent event in said event queue.

13. The method as recited in claim 8 further comprising:

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

14. The method as recited in claim 8 further comprising:

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

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

intercepting a request to publish a new event 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; and

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

16. The method as recited in claim 15 further comprising:

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

17. The method as recited in claim 15 wherein a given event becomes de-queued from said event queue in response to all subscribers that expressed an interest in said given event having consumed said given event.

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

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

20. The method as recited in claim 15 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.

21. The method as recited in claim 15 further comprising:

propagating said new event to said subscriber.