METHOD AND SYSTEM FOR MANAGING DATA TRANSACTION REQUESTS

• US 20100094919A1
• Filed: 12/14/2009
• Published: 04/15/2010
• Est. Priority Date: 07/03/2003
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: eBay Inc.
• Inventors: Seitz, Greg, Kasten, Christopher J., Grossfeld, Elena, Lockert, Thorsten, Widjojo, Surjatini, Wigginton, Kenneth Randall
• Granted Patent: US 7,941,469 B2
• Time in Patent Office: Days
• US Class Current: 707/826
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: Y10S 707/966 Distributed
• CPC Class Codes: Y10S 707/968 Partitioning
• CPC Class Codes: Y10S 707/969 Horizontal partitioning

Abstract

In one embodiment, a method is provided for processing data transactions in a data store that includes databases. In this method, a data transaction request is received from a requesting computer. Different databases are then identified from the databases using a data access layer that defines an abstraction layer. The data transmission request is then split into multiple data transaction requests, and a part of these requests is then communicated to at least one of the identified databases.

Claims

1. A system to process data transactions in a data store including a plurality of databases, the system comprising:

a processor-implemented computer interface module to receive a data transaction request from at least one requesting computer;

a processor-implemented data store interface module to interface the system to the plurality of databases; and

a processor-implemented data access layer to identify a plurality of different databases from the plurality of databases and to split the data transaction request into a plurality of data transaction requests to the plurality of different databases, the processor-implemented data access layer being operatively in data communication with the processor-implemented computer interface module and the processor-implemented data store interface module and defining an abstraction layer between the processor-implemented computer interface module and the processor-implemented data store interface module.

2. The system of claim 1, wherein the data transaction request is an object oriented request and the plurality of databases are horizontally distributed, the processor-implemented data access layer defining an object oriented abstraction layer between the processor-implemented computer interface module and the plurality of databases.

3. The system of claim 1, wherein the processor-implemented data access layer comprises a plurality of logical hosts and a plurality of physical hosts, wherein a logical host in the plurality of logical hosts is derived from the data transaction request and mapped to a physical host that identifies at least one of the plurality of databases.

4. The system of claim 3, wherein the processor-implemented data access layer comprises at least one logical table and at least one physical table, the at least one logical table being identified from the data transaction request and mapped to the at least one physical table which identifies a corresponding logical host.

5. The system of claim 1, further comprising a processor-implemented data dependent routing module that generates a query to at least one of the plurality of different databases that is identified based on content of the data in the data transaction request.

6. The system of claim 5, wherein the processor-implemented data dependent routing module identifies a data type from the data transaction request and maps the data transaction request to an associated physical host based on the at least one rule.

7. The system of claim 6, wherein the at least one rule includes at least one attribute that is used to identify the physical host.

8. The system of claim 5, wherein data associated with a user is split across the plurality of databases and the processor-implemented data dependent routing module identifies at least one database associated with the user from the data transaction request.

9. The system of claim 5, wherein the data transaction request is an object oriented request and the processor-implemented data dependent routing module maps the object oriented request to a physical host that identifies an associated database of the plurality of databases.

10. The system of claim 1, which forms part of a network-based commerce facility and the data transaction requests are requests associated with items listed in the network-based commerce facility, the data transaction requests being communicated between any one of a plurality of client machines and the system via the Internet.

11. A method of processing data transactions in a data store including a plurality of databases, the method comprising:

receiving a data transaction request from at least one requesting computer;

using a data access layer that defines an abstraction layer to identify a plurality of different databases from the plurality of databases;

splitting the data transaction request, using at least one processor, into a plurality of data transaction requests;

communicating at least part of the plurality of data transaction requests to at least one database of the plurality of different databases identified;

gathering a plurality of results received from the different databases; and

presenting the plurality of results to the at least one requesting computer.

12. The method of claim 11, wherein the data transaction request is an object oriented request and the plurality of databases are horizontally distributed, the method comprising defining an object oriented abstraction layer between the requesting computer and the plurality of databases.

13. The method of claim 11, wherein the data access layer comprises a plurality of logical hosts and a plurality of physical host, the method comprising deriving a logical host from the plurality of logical hosts from the data transaction request and mapping the logical host to a physical host that identifies at least one of the plurality of different databases.

14. The method of claim 13, wherein the data access layer comprises at least one logical table and at least one physical table, the method comprising identifying the at least one logical table from the data transaction request and mapping the at least one logical table to the at least one physical table which identifies a corresponding logical host.

15. The method of claim 11, further comprising generating a query to at least one of the plurality of different databases that is identified based on content of the data in the data transaction request.

16. The method of claim 11, further comprising identifying a data type from the data transaction request and mapping the data transaction request to an associated database of the plurality of databases according to at least one rule.

17. The method of claim 16, further comprising optionally changing the at least one rule in real-time.

18. The method of claim 16, further comprising:

identifying if the data transaction request has an associated rule;

retrieving the associated rule when the data transaction request has a rule associated therewith; and

mapping the data transaction request to a physical host based on the associated rule.

19. The method of claim 18, wherein the mapping of the data transaction request to a physical host includes:

mapping the data transaction request to a logical host based on the associated rule; and

mapping the logical host to a physical host identifying one of the plurality of databases.

20. The method of claim 16, wherein the at least one rule includes an attribute that is used identify a physical host.

21. The method of claim 11, wherein data associated with a user is split across the plurality of databases, the method comprising identifying at least one database associated with the user from the data transaction request.

22. The method of claim 11, wherein the data transaction request is an object-orientated request, the method comprising mapping the object-orientated request to a physical host that identifies an associated database of the plurality of databases.

23. The method of claim 11, further comprising determining whether at least one of the plurality of different databases identified is down and, based on the determining, mapping the data transaction request to an alternative database of the plurality of different databases.

24. The method of claim 11, wherein the data transaction request comprises one or more of a create transaction, a read transaction, an update transaction, and a delete transaction and the data access layer is programmable to define in which database of the plurality of databases the transaction is to be performed in.

25. The method of claim 11, further comprising:

monitoring the status of the plurality of databases; and

using the data access layer to balance a load on the plurality of databases in response to the monitored status.

26. A system to process data transactions in a data store including a plurality of databases, the system comprising:

means for receiving a data transaction request from at least one requesting computer;

means for using a data access layer that defines an abstraction layer to identify a plurality of different databases from the plurality of databases and to split the data transaction request into a plurality of data transaction requests; and

means for communicating at least part of the plurality of data transaction request to the at least one database of the plurality of different databases identified.

27. The system of claim 26, wherein the data transaction request is an object oriented request and the plurality of databases are horizontally distributed, the data access layer defining an object oriented abstraction layer between the means for receiving a data transaction request and the plurality of databases.

28. The system of claim 26, further comprising data dependent routing means for generating a query to at least one of the plurality of different databases that is identified based on content of the data in the data transaction request.

29. A machine-readable storage medium which comprises instructions that, when executed by a machine, cause the machine to:

receive a data transaction request from at least one requesting computer;

use a data access layer that defines an abstraction layer to identify at least one database from the plurality of databases and to split the data transaction request into a plurality of data transaction requests; and

communicate at least part of the plurality of data transaction requests to the at least one database of the plurality of different databases identified.