Database system and method of optimizing cross database query
View Patent ↗A database system and a method of optimizing cross-database query. The database system includes a plurality of databases. At least two of the databases are stored with one or more data collections composed of tables with the same structure. A federated view of the data collection is created on each of the databases. A request routing layer for routing, in response to a query request crossing the data collections, the query request crossing the data collections to one of the at least two databases according to a predetermined routing rule, so as to query by using the federated view of the database.
1. A database system comprising:
a plurality of databases, at least two of the plurality of databases are stored with one or more data collections composed of tables with the same structure, a federated view of the data collection is created, by at least one computer processor, on each of the at least two databases; and
a request routing layer for routing, in response to a query request crossing the data collections, the query request crossing the data collections to one of the at least two databases according to a predetermined routing rule, so as to query by using the federated view of the database;
wherein the predetermined routing rule comprises: a first routing rule for routing a cross-tenant data query request from a tenant to the database in which tenant data of the tenant is located, a second routing rule for routing a cross-tenant data query request from a tenant to the database in which most of tenant data involved is located and a third routing rule for routing a cross-tenant data query request to the database with the lowest load based on the status of the databases.
2. The database system according to claim 1 , wherein the database system is a Software-as-a-Service (SaaS) database system, and each of the data collections is a collection of data in the SaaS database system that is referred to as tenant data and belongs to one tenant.
3. The database system according to claim 2 , further comprising:
a request tracker for tracking a cross-tenant data query request behavior in runtime; and
a tenant data mover for moving tenant data among the plurality of databases in off-line time based on the tracking result of the request tracker.
4. The database system according to claim 3 , wherein the tracking a cross-tenant data query request behavior comprises tracking frequency of query by each tenant involving other tenants.
5. The database system according to claim 3 , wherein the tenant data mover further moves tenant data among the plurality of databases based on the status of the databases.
6. The database system according to claim 1 , wherein the status of the database comprises at least loads and response speed to query of the database.
7. The database system according to any one of claim 1 , wherein the database is a distributed database.
8. The database system according to claim 1 , wherein the query request crossing data collections is a SQL statement, and the SQL statement can contain a function.
9. A computer implemented method of optimizing cross-database query in a database system comprising a plurality of databases, at least two of the plurality of databases are stored with one or more data collections composed of tables with the same structure, the method comprising the steps of:
a federated view creating step for creating a federated view of the data collections on each of the at least two databases; and
a routing step for routing, in response to a query request crossing the data collections, the query request crossing the data collections to one of the at least two databases according to a predetermined routing rule so as to query by using the federated view of the database;
wherein the predetermined routing rule comprises: a first routing rule for routing a cross-tenant data query request from a tenant to the database in which tenant data of the tenant is located, a second routing rule for routing a cross-tenant data query request from a tenant to the database in which most of tenant data involved is located and a third routing rule for routing a cross-tenant data query request to the database with the lowest load based on the status of the databases.
10. The computer implemented method of optimizing cross-database query according to claim 9 , wherein the database system is a Software-as-a-Service (SaaS) database system, and each of the data collections is a collection of data in the SaaS database system that is referred to as tenant data and belongs to one tenant.
11. The computer implemented method of optimizing cross-database query according to claim 9 , further comprising:
tracking a cross-tenant data query request behavior in runtime; and
moving tenant data among the plurality of databases in off-line time based on the tracking result of the cross-tenant data query request behavior.
12. The computer implemented method of optimizing cross-database query according to claim 11 , further moving tenant data among the plurality of databases based on the statuses of the databases.
13. The computer implemented method of optimizing cross-database query according to claim 11 , wherein the tracking a cross-tenant data query request behavior comprises tracking frequency of query by each tenant involving other tenants.
14. The computer implemented method of optimizing cross-database query according to claim 9 , wherein the status of the database comprises at least loads and response speed to query of the database.
15. The computer implemented method of optimizing cross-database query according to any one of claim 9 , wherein the database is a distributed database.
16. The computer implemented method of optimizing cross-database query according to claim 9 , wherein the query request crossing data collections is a SQL statement, and the SQL statement can contain a function.