METHOD AND SYSTEM FOR MANAGING DATA TRANSACTION REQUESTS

• US 20110208793A1
• Filed: 05/09/2011
• Published: 08/25/2011
• 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 8,291,000 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 various embodiments, a system, method, and related computer-related medium to process data transactions are provided. In one example, a system is arranged to process data transactions in a data store including a plurality of databases. The system includes a computer interface module to receive a data transaction request from at least one requesting computer and a data access layer having one or more processors to identify at least one database in the plurality of databases. The data access layer is to define an abstraction layer between a computer interface module and the plurality of databases.

Claims

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

a computer interface module to receive a data transaction request from at least one requesting computer; and

a data access layer having one or more processors to identify at least one database in the plurality of databases, the data access layer to define an abstraction layer between a computer interface module and the plurality of databases.

2. The system of claim 1, wherein the data transaction request is an object oriented request and the plurality of databases is horizontally distributed, the data access layer is further to define an object oriented abstraction layer between the computer interface module and the plurality of databases.

3. The system of claim 1, wherein the data access layer comprises a plurality of logical hosts and a plurality of physical hosts, the data access layer is further to derive a logical host from the data transaction request and map the data transaction request to a physical host to identify at least one of the plurality of databases.

4. The system of claim 1, wherein the data access layer comprises at least one logical table and at least one physical table, the data access layer is further to identify a logical table from the data transaction request and map the data transaction request to a physical table to identify a corresponding logical host.

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

6. The system of claim 5, wherein the data dependent routing module is to identify a data type from the data transaction request and map the data transaction request to an associated physical host based on at least one rule.

7. The system of claim 6, wherein the at least one rule includes at least one attribute used 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 data dependent routing module is further to identify at least one of the plurality of databases from the data transaction request.

9. The system of claim 5, wherein the data transaction request is an object oriented request and the data dependent routing module is to map the object oriented request to a physical host to identify an associated database of the plurality of databases.

10. The system of claim 1, where the system is part of a network-based commerce facility and the data transaction request is a request associated with items listed in the network-based commerce facility, the data transaction request 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; and

using a data access layer that defines an abstraction layer to identify, using one or more processors, at least one database from the plurality of databases.

12. The method of claim 11, wherein the data transaction request is an object oriented request and the plurality of databases is horizontally distributed, the method further comprising defining an object oriented abstraction layer between the at least one 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 further comprising:

deriving a logical host from the data transaction request; and

mapping the logical host to a physical host that identifies at least one of the plurality of databases.

14. The method of claim 11, wherein the data access layer comprises at least one logical table and at least one physical table, the method further comprising:

identifying a logical table from the data transaction request; and

mapping the logical table to a physical table which identifies a corresponding logical host.

15. The method of claim 11, further comprising generating a query to a database that is identified based on content of 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 changing the at least one rule in real-time.

18. The method of claim 16, further comprising:

making a determination if the data transaction request has an associated rule; and

based on the determination that the data transaction request has the associated rule;

retrieving the associated rule; and

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

19. The method of claim 18, wherein mapping 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 in identifying a physical host.

21. The method of claim 11, wherein data associated with a user is split across the plurality of databases, the method further 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 further comprising mapping the object-orientated request to a physical host, the physical host identifying an associated database of the plurality of databases.

23. The method of claim 11, further comprising:

making a determination if the identified database is down; and

based on the determination that the identified database is down, mapping the data transaction request to an alternative database of the plurality of databases.

24. The method of claim 11, further comprising:

monitoring a 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.

25. The method of claim 11, further comprising:

splitting a data transaction request to different databases of the plurality of databases; and

gathering results received from the different databases and presenting them to the requesting computer.

26. A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors, cause the machine to perform operations comprising:

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

using a data access layer that defines an abstraction layer to identify at least one database from the plurality of databases.