Scalable multi-database event processing system using universal subscriber-specific data and universal global data

• US 7,406,471 B1
• Filed: 09/27/2001
• Issued: 07/29/2008
• Est. Priority Date: 09/28/2000
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Shankar, Ravi, Brefczynski, Keith M.
• Primary Examiner(s): Lu; Kuen S
• Application Number:
  US09/967,493
• Time in Patent Office: 2,497 Days
• Field of Search: 713/200, 707/10, 707/5, 707/2, 707/4, 707/104.1
• US Class Current: 1/1
• 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
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

Methods and architectures for implementing a scalable multi-database event processing system are provided. In one embodiment, selected account data is aggregated for all subscribers (aggregated subscriber-specific data) and a copy included on each database. In one embodiment, selected data that is not subscriber specific and that may apply to many accounts (“global data”) is also maintained and copied to each database. The global data preferably includes business data that is frequently required during operation of the system, such as pricing data. A transaction that requires business data and access to an account is processed using the copy of the business data that is on the database on which the account is located. In an embodiment, the aggregated subscriber-specific data is used in performing searches.

Claims

1. A method for processing an event in an event processing system comprising a plurality of databases, wherein the event processing system is associated with a plurality of accounts, and wherein each database in the plurality of databases is configured to store account data for a unique subset of accounts in the plurality of accounts, the method comprising:

receiving, at a first server configured to manage a first database in the plurality of databases, an event associated with an account in the plurality of accounts,

wherein processing the event requires access to account data for the account, and

wherein the first database stores account data for a first subset of accounts;

if the account is included in the first subset of accounts, retrieving the account data for the account from the first database;

else if the account is not included in the first subset of accounts;

accessing a data structure stored on the first database,

wherein the data structure includes, for each account in the plurality of accounts, an identifier uniquely identifying said each account and location information indicating a database in the plurality of databases on which account data for said each account is stored;

determining, based on the data structure, a second database in the plurality of databases that stores the account data for the account,

wherein the second database stores account data for a second subset of accounts distinct from the first subset; and

retrieving the account data for the account from the second database; and

processing the event utilizing the account data for the account.

2. The method of claim 1, wherein the data structure is stored on each of the databases of the multi-database event processing system.

3. A method as in claim 1, wherein a two step commit is not utilized.

4. The method of claim 1 wherein processing the event further requires access to global information that is independent of the account, wherein a master copy of the global information is stored on a third database in the plurality of databases, wherein a replicated copy of the global information is stored on the first database, and wherein processing the event utilizing the account data for the account comprises:

accessing the replicated copy of the global information stored on the first database; and

processing the event utilizing the account data for the account and the replicated copy of the global information, such that the event is processed without accessing the master copy of the global information stored on the third database.

5. A method as in claim 1, wherein the event processing system is an accounting system.

6. A machine-readable medium for a computer system, the machine-readable medium having stored thereon a series of instructions which, when executed by a processing component, cause the processing component to process an event in an event processing system comprising a plurality of databases, wherein the event processing system is associated with a plurality of accounts, and wherein each database in the plurality of databases is configured to store account data for a unique subset of accounts in the plurality of accounts, by:

receiving, at a first server configured to manage a first database in the plurality of databases, an event associated with an account in the plurality of accounts,

wherein processing the event requires access to account data for the account, and

wherein the first database stores account data for a first subset of accounts;

if the account is included in the first subset of accounts, retrieving the account data for the account from the first database;

else if the account is not included in the first subset of accounts;

accessing a data structure stored on the first database,

wherein the data structure includes, for each account in the plurality of accounts, an identifier uniquely identifying said each account and location information indicating a database in the plurality of databases on which account data for said each account is stored;

determining, based on the data structure, a second database in the plurality of databases that stores the account data for the account,

wherein the second database stores account data for a second subset of accounts distinct from the first subset; and

retrieving the account data for the account from the second database; and

processing the event utilizing the account data for the account.

7. The machine-readable medium of claim 6, wherein the machine-readable medium is one of a CD-ROM, floppy disk, tape, flash memory, system memory, hard drive, or data signal embodied in a carrier wave.

8. The machine-readable medium of claim 6 further comprising:

replicating the data structure on the first database to another database of the multi-database event processing system.

9. The machine-readable medium of claim 6 wherein processing the event further requires access to global information that is independent of the account, wherein a master copy of the global information is stored on a third database in the plurality of databases, wherein a replicated copy of the global information is stored on the first database, and wherein processing the event utilizing the account data for the account comprises:

accessing the replicated copy of the global information stored on the first database; and

processing the event utilizing the account data for the account and the replicated copy of the global information, such that the event is processed without accessing the master copy of the global information stored on the third database.

10. The machine-readable medium of claim 9, wherein the machine-readable medium is one of a CD-ROM, floppy disk, tape, flash memory, system memory, hard drive, or data signal embodied in a carrier wave.