System and method for implementing on demand cloud database

• US 8,832,130 B2
• Filed: 10/12/2010
• Issued: 09/09/2014
• Est. Priority Date: 08/19/2010
• Status: Active Grant

• Current Assignee: Infosys Limited
• Original Assignee: Infosys Limited
• Inventors: Doddavula, Shyam Kumar, Pratap Singh, Abhishek
• Primary Examiner(s): PHAM, KHANH B
• Application Number:
  US12/902,298
• Publication Number:
  US 20120047107A1
• Time in Patent Office: 1,428 Days
• Field of Search: 707/759, 707/769, 707/770
• US Class Current: 707/759
• 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: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning
• CPC Class Codes: G06F 2209/5019 Workload prediction
• CPC Class Codes: G06F 9/5083 Techniques for rebalancing the load in a distributed system

Abstract

A method for dynamic management of one or more cloud database nodes is provided. The method enables gathering information related to usage of one or more cloud database nodes. The method further enables comparing time required by the one or more cloud database nodes for responding to one or more requests with a predetermined threshold. Furthermore, the method enables provisioning one or more new cloud database nodes or removing one or more new cloud database nodes based on at least one of: the gathered information, the comparison and a combination thereof.

Claims

1. A method for interacting with dynamically scaled cloud database architecture, the method comprising the steps of:

receiving one or more requests by a cloud database client;

converting the one or more requests to a query language format;

locating one or more cloud database server instances;

sending the one or more converted requests to at least one of the located cloud database server instance;

processing the one or more converted requests at the located cloud database server instance, the processing comprising;

interpreting the one or more converted requests based on;

entity identifications associated with the converted requests and creation of selection criteria based on one or more characteristics of entities associated with the converted requests for selecting a group of entities, if the entity identifications associated with the converted requests are not identified;

identifying one or more entities corresponding to the one or more converted requests based on the interpretation;

determining one or more cloud database node instances that store the identified entities;

routing the one or more converted requests to the determined one or more cloud database node instances, wherein the determined one or more cloud database node instances comprises at least one of;

one or more cloud database node instances storing related entities corresponding to the identified entities and one or more cloud database node instances storing replicated entities corresponding to the identified entities;

receiving, at the located cloud database server instance, one or more results from the determined one or more cloud database node instances, wherein the one or more results comprise the identified entities; and

sending the one or more results to the cloud database client.

2. The method of claim 1, wherein converting the one or more requests to a query language format comprises capturing the one or more requests in a query object.

3. The method of claim 1, wherein locating the one or more cloud database server instances comprises locating at least one of:

existing cloud database server instances and provisioned cloud database server instances.

4. The method of claim 1, wherein sending the converted requests to at least one of the located cloud database server instance comprises serializing the converted requests into a sequence of bits.

5. The method of claim 4, wherein processing the one or more converted requests at the cloud database server instance comprises deserializing the sequence of bits to obtain the converted requests.

6. The method of claim 1, wherein routing the one or more converted requests to the determined one or more cloud database node instances comprises routing the one or more requests to the determined one or more cloud database node instances via one or more other cloud database server instances.

7. The method of claim 1, wherein receiving results from the one or more cloud database node instances comprises aggregating results corresponding to the one or more converted requests received from the one or more cloud database node instances.

8. A system for facilitating interaction with dynamically scaled cloud database architecture, the system comprising:

a cloud database client in communication with a processor and configured to receive and convert one or more requests to a query language format;

a cloud database server in communication with a processor and configured to receive the query language format from the cloud database client and process the query language format to;

interpret the one or more converted requests based on;

entity identifications associated with the converted requests and creation of selection criteria based on one or more characteristics of entities associated with the converted requests for selecting a group of entities, if the entity identifications associated with the converted requests are not identified;

identify one or more entities corresponding to the one or more converted requests based on the interpretation; and

determine one or more cloud database node instances that store the identified entities,

the cloud database server comprising;

a routing module in communication with a processor and configured to route the one or more converted requests to the determined one or more cloud database node instances, wherein the determined one or more cloud database node instances comprises at least one of;

one or more cloud database node instances storing related entities corresponding to the identified entities and one or more cloud database node instances storing replicated entities corresponding to the identified entities;

and

the one or more cloud database node instances in communication with a processing engine and configured to provide one or more results to the cloud database client corresponding to the one or more converted requests via at least one of the cloud database server and other cloud database server instances, the results being the identified entities.

9. The system of claim 8, wherein the cloud database client comprises a query store client that receives and converts the one or more requests to a query language format using a Java Persistence API (Application Programming Interface) Adaptor.

10. The system of claim 8, wherein the cloud database client comprises a Serialization De-Serialization module configured to:

translate the one or more converted requests into a sequence of bits; and

send the sequence of bits to the cloud database server over a network.

11. The system of claim 8, wherein the cloud database client comprises an Inconsistency Resolver configured to resolve inconsistencies in the one or more results received from the cloud database server.

12. The system of claim 11, wherein the Inconsistency Resolver comprises a Resolve by Identification (Id) module configured to resolve inconsistencies in the one or more results by updating version identification numbers associated with the entities stored in the one or more cloud database node instances.

13. The system of claim 11, wherein the Inconsistency Resolver comprises a Resolve by Time module configured to resolve inconsistencies in the one or more results by identifying latest version of entities stored in the one or more cloud database node instances based on modified time information associated with the entities.

14. The system of claim 8, wherein the cloud database server is configured to send the one or more requests to one or other cloud database server instances.

15. The system of claim 8, wherein the cloud database server comprises a Query Processor configured to interpret the one or more converted requests.

16. The system of claim 15, wherein the Query Processor comprises Query by Identification module configured to interpret the one or more converted requests based on the entity identifications associated with the converted requests.

17. The system of claim 15, wherein the Query Processor comprises Query by Criteria module configured to interpret the one or more requests based on the selection criteria for the entities created based on the one or more characteristics of the one or more converted requests.

18. The system of claim 8, wherein the routing module is configured to reparation entities across one or more of the existing and provisioned cloud database node instances.

19. A computer program product comprising:

a non-transitory computer-readable medium having computer-readable program code stored thereon, the computer-readable program code having program instructions, when executed by one or more processors, cause the one or more processors to;

receive one or more requests by a cloud database client;

convert the one or more requests to a query language format;

locate one or more cloud database server instances;

send the one or more converted requests to at least one of the located cloud database server instance;

process the one or more converted requests at the located cloud database server instance, wherein the processing comprises;

interpreting the one or more converted requests based on;

entity identifications associated with the converted requests and creation of selection criteria based on one or more characteristics of entities associated with the converted requests for selecting a group of entities, if the entity identifications associated with the converted requests are not identified;

identifying one or more entities corresponding to the one or more converted requests based on the interpretation;

determining one or more cloud database node instances that store the identified entities;

route the one or more converted requests to the determined one or more cloud database node instances, wherein the determined one or more cloud database node instances comprises at least one of;

one or more cloud database node instances storing related entities corresponding to the identified entities and one or more cloud database node instances storing replicated entities corresponding to the identified entities;

receive the one or more results from the determined one or more cloud database node instances, wherein the one or more results comprise the identified entities; and

send the one or more results to the cloud database client.

20. The system of claim 19, wherein the cloud database server further comprises an entity helper in communication with the processor and configured to maintain information regarding relationship among related entities which are partitioned and stored across the cloud database instances.