WO2014063474A1 - Database extension method, database extension device and database system - Google Patents

Abstract

Proposed are a database extension method, a database extension device and a database system. The method is applied to a database system comprising a load balancer and a main database, and comprises: the load balancer creating a sub-database; and the load balancer sending a first data synchronization instruction to the main database so as to enable the main database to synchronize data stored therein to the sub-database, the main database being a database which allows a user to perform data read and write operations; the sub-database being a database which only allows a user to perform a data read operation.

Description

 Database extension method, database extension device and database system

 The present invention relates to the field of information technology, and in particular, to a database extension method, a database extension device, and a database system. Background technique

 In database access management, how to flexibly expand the database according to changes in user access is a problem that needs to be solved.

 In the existing solutions such as SharePoint, by dividing the database into different business databases, all read/write requests of the user are distributed to a specific database according to the interface layer, so that the access is divided to balance the load of each database. The purpose of quantity. However, the disadvantage of this solution is that if the database is flexibly increased, the problem of inconsistent data reading and writing will occur. Therefore, the service can only be provided based on the database already set, and the database cannot be flexibly increased in response to the increase in the amount of user access. The shunt problem cannot be solved very well. Summary of the invention

 Problems to be solved by the invention

 In view of the above, an object of the present invention is to provide a database expansion method, a database expansion device, and a database system capable of expanding a database while ensuring data consistency.

 Solution to solve the problem

To achieve the above objective, in a first aspect, an embodiment of the present invention provides a database extension method, which is applied to a database system including a load balancer and a primary database, where the method includes: The load balancer creates a sub-database;

 The load balancer sends a first data synchronization instruction to the primary database to cause the primary database to synchronize data stored by the primary database to the sub-database;

 The primary database is a database that allows a user to perform data read and write operations; the secondary database is a database that allows only users to perform data read operations.

 With reference to the first aspect, in a first possible implementation, the method further includes: the load balancer receiving a data write request;

 The load balancer sends a data write instruction to the primary database to write the requested data to the primary database according to the data write request; the load balancer sends a second to the primary database The data synchronization instruction, in combination with the first aspect or the first possible implementation manner of the first aspect, in the second possible implementation manner, the method further includes:

 The load balancer receives a data read request;

 The load balancer selects a matching database from the primary database and the sub-database according to a database system access policy;

 The load balancer sends a data read instruction to the matching database to read the requested data from the matching database.

 In conjunction with the second possible implementation manner, in a third possible implementation, the database system access policy includes at least one of a database system access load balancing policy and a database system access speed policy.

 In a second aspect, an embodiment of the present invention provides a database expansion apparatus, which is applied to a database system including a primary database, where the apparatus includes:

 Create a unit for creating a subdatabase;

a sending unit, configured to send a first data synchronization instruction to the primary database, Causing the primary database to synchronize data stored by the primary database to the sub-database;

 The primary database is a database that allows a user to perform data read and write operations; the secondary database is a database that allows only users to perform data read operations.

 With reference to the second aspect, in a first possible implementation, the method further includes a receiving unit, where the receiving unit is configured to receive a data write request, and the sending unit is further configured to: according to the data write request, to the The primary database sends a data write instruction to write the requested data to the primary database and to send a second data synchronization instruction to the primary database to cause the primary database to synchronize the written data to the Subdatabase.

 With reference to the first possible implementation manner of the second aspect, in a second possible implementation, the method further includes a selecting unit, where the receiving unit is further configured to receive a data read request, where the selecting unit is configured to use the database system Accessing a policy, selecting a matching database from the primary database and the sub-database;

 The sending unit is further configured to send a data read instruction to the matched database to read the requested data from the matched database; wherein the database system access policy includes a database system access load balancing policy and a database At least one of system access speed policies.

 In a third aspect, an embodiment of the present invention provides a database system, including a load balancer and a primary database, where: the load balancer creates a sub-database, and sends a first data synchronization instruction to the primary database; Receiving, by the database, the first data synchronization instruction, and synchronizing the data stored by the primary database to the sub-database; wherein the primary database is a database that allows a user to perform data read and write operations; A database in which users perform data read operations.

With reference to the third aspect, in a first possible implementation, the method further includes: the load balancer receiving a data write request, and writing according to the data Requesting to send a data write instruction to the primary database;

 The primary database receives the data write instruction and writes the requested data to the primary database;

 The load balancer sends a second data synchronization instruction to the primary database; and

 The primary database receives the second data synchronization instruction and synchronizes the written data to the sub-database.

 With reference to the third aspect, or the first possible implementation manner of the third aspect, in a second possible implementation, the method further includes: the load balancer receiving a data read request, according to a database system access policy from the main And the database and the sub-database select a matching database, and send a data read instruction to the matched database; the matched database receives the data read instruction, and provides the requested data according to the data read instruction The database system access policy includes at least one of a database system access load balancing policy and a database system access speed policy.

 The database extension method, device and database system provided by the embodiment of the invention, by creating a sub-database, send a data synchronization instruction to the main database, and synchronize the data stored in the main database to the sub-database, thereby being flexible and not flexible. Database extensions while ensuring data consistency.

 Other features and advantages of the present invention will be apparent from the following description of the accompanying drawings. The specific principle of the invention. DRAWINGS

It should be understood that the appended drawings are not necessarily A somewhat simplified representation of the various features of the basic principles of the invention. The specific design features of the invention disclosed herein, including, for example, specific dimensions, orientations, positions and shapes, are determined in part by the particular application and use environment.

 1 shows a flow diagram of a database extension method in accordance with one embodiment of the present invention;

 2 shows a flow chart of write data processing of a database extension method in accordance with one embodiment of the present invention;

 Figure 3 is a flow chart showing the processing of read data of the database extension method in accordance with one embodiment of the present invention;

 Figure 4 is a block diagram showing a database expansion apparatus in accordance with one embodiment of the present invention;

 Figure 5 is a block diagram showing a database expansion apparatus according to another embodiment of the present invention;

 Figure 6 is a block diagram showing a database expansion apparatus according to another embodiment of the present invention;

 Figure 7 shows a block diagram of a database system in accordance with one embodiment of the present invention. detailed description

 Reference will now be made in detail to the embodiments of the invention, While the present invention has been described in connection with the exemplary embodiments, it is understood that this description is not intended to limit the invention. Rather, the invention is not limited to the embodiments of the invention, and the various alternatives, modifications, equivalents, and other embodiments, which are included within the scope and scope of the invention as defined by the appended claims.

1 shows a flow of a database extension method in accordance with one embodiment of the present invention. In this embodiment, the method is applied to a database system including a load balancer and a primary database, and mainly includes the following steps:

 5101. The load balancer creates a sub-database.

 S102: The load balancer sends a first data synchronization instruction to the primary database, so that the primary database synchronizes data stored by the primary database to the sub-database.

 The primary database is a database that allows a user to perform data read and write operations; the secondary database is a database that allows only users to perform data read operations.

 In this embodiment, by creating a sub-database, a data synchronization instruction is sent to the primary database, and the data stored in the primary database is synchronized to the sub-database, thereby realizing the expansion of the database and ensuring data consistency.

 Preferred embodiments of the steps of this embodiment are described in detail below.

 In step S101, the number of primary databases may be one or more, and each primary database may only store specific types of data, and may also save various types of data at the same time, so accessing and expanding the database is not stored by the database. limits. In addition, it is preferable to create a primary database before any database extensions are performed, and it is preferable to create a primary database when the database system is originally designed.

 In a preferred embodiment, in step S101, the load balancer can flexibly create a sub-database based on the user's access to the primary database. For example, when a user's access to the primary database exceeds the load threshold of the primary database, the load balancer can create one or more subdatabases.

 The load balancer can create a sub-database in various ways. For example, the load balancer can enable one or more standby databases as a sub-database according to the amount of access, and the like.

In step S102, the load balancer sends a first data synchronization instruction to the primary database to synchronize the data stored by the primary database by the primary database. To the sub-database; thereby maintaining data consistency between the primary database and the sub-database while the database is expanding.

 Figure 2 is a flow chart showing the write data processing of the database extension method in accordance with one embodiment of the present invention. The write data processing includes:

 5201. The load balancer receives a data write request.

 S202, the load balancer sends a data write instruction to the primary database according to the received data write request, to write the requested data into the primary database;

 5203. The load balancer sends a second data synchronization instruction to the primary database, so that the primary database synchronizes the written data to the sub-database.

 Preferably, in a case where there are a plurality of primary databases, in step S202, the load balancer may select a matching database from the plurality of primary databases according to the database system access policy and send a data write command.

 3 is a flow chart showing the processing of read data of the database extension method according to an embodiment of the present invention. In this embodiment, the read data processing includes:

S301: The load balancer receives a data read request.

 S302: The load balancer selects a matching database from the primary database and the sub-database according to a database system access policy.

 5303. The load balancer sends a data read command to the matched database to read the requested data from the matched database.

 In a preferred embodiment, when receiving the data read request, the load balancer can select only the matching database from the sub-database, thereby implementing read-write splitting, thereby further improving the overall load capacity of the database while maintaining Data consistency.

Preferably, the database system access policy includes at least one of a database system access load balancing policy and a database system access speed policy. for example, According to the database system load balancing policy, the load balancer can select a matching database according to each database load condition based on load balancing technology such as elastic load balancing; according to the database system access speed policy, the load balancer can be based on, for example, DNS (Domain Name System, Domain Name System ) Performs intelligent matching, selecting the nearest database for the user who sent the request, such as selecting a matching telecommunications database for telecommunications network users, and so on.

 Preferably, the load balancer can support various protocol types, and supports corresponding session keeping policies and health check mechanisms, thereby providing multiple protocols and service support, and implementing load balancing of various services such as Exchange, sharepoint, and SAP, and Widely used in public and private cloud scenarios.

 4 is a block diagram showing a database expansion apparatus 400 in accordance with an embodiment of the present invention. In this embodiment, the apparatus is applied to a database system including a primary database, and mainly includes:

 Creating a unit 401 for creating a sub-database;

 The sending unit 402 is configured to send a first data synchronization instruction to the primary database, so that the primary database synchronizes data stored by the primary database to the sub-database;

 The primary database is a database that allows a user to perform data read and write operations; the secondary database is a database that allows only users to perform data read operations.

 The database expansion apparatus provided by the embodiment of the present invention can implement load balancing by creating a sub-database and synchronizing the main database data to the sub-database.

FIG. 5 is a structural diagram of a database expansion apparatus 500 according to another embodiment of the present invention. The database expansion apparatus 500 of the embodiment further includes a receiving unit 403 for receiving on the basis of the embodiment shown in FIG. Data write request. And sending a data write instruction to the primary database to write the requested data to the a primary database, and transmitting a second data synchronization instruction to the primary database to cause the primary database to synchronize the written data to the secondary database.

 FIG. 6 shows a structural diagram of a database expansion apparatus 600 according to another embodiment of the present invention. The database expansion apparatus 600 of the embodiment further includes a selection unit 404, the receiving unit, based on the embodiment shown in FIG. The unit 403 is further configured to receive a data read request; the selecting unit 404 is configured to select a matching database from the primary database and the sub-database according to a database system access policy; the sending unit 402 is further configured to The matching database sends a data read instruction to read the requested data from the matched database; wherein the database system access policy includes at least one of a database system access load balancing policy and a database system access speed policy.

 Preferably, the selecting unit 404 can select only the matched database from the sub-database to implement read-write and shunt to further improve the overall load capacity of the database while maintaining data consistency.

 Figure 7 shows a database system 700 including a load balancer 701 and a primary database 702 in accordance with one embodiment of the present invention, wherein:

 The load balancer 701 creates a sub-database 703 and sends a first data synchronization instruction to the main database 702;

 The primary database 702 receives the first data synchronization instruction, and synchronizes the data stored by the primary database 702 to the sub-database 703;

 The primary database 702 is a database that allows users to perform data read and write operations; the secondary database 703 is a database that allows only users to perform data read operations.

In a preferred embodiment, the load balancer 701 receives a data write request and sends a data write command to the primary database 702 according to the data write request; the primary database 702 receives the data write Directing, and writing the requested data to the primary database 702; the load balancer 701 to the primary database 702 transmits a second data synchronization instruction; and the primary database 702 receives the second data synchronization instruction and synchronizes the written data to the sub-database 703.

 In another preferred embodiment, the load balancer 701 receives a data read request, selects a matching database from the primary database 702 and the sub-database 703 according to a database system access policy, and sends the matched database to the matched database. a data read instruction; the matched database receives the data read instruction, and provides the requested data according to the data read instruction; wherein the database system access policy includes a database system access load balancing policy and a database system At least one of the access speed policies.

 Preferably, the load balancer 701 can select only the matching database from the sub-database 703, thereby implementing read-write and offloading, further improving the overall load capacity of the database while maintaining data consistency.

 The specific exemplary embodiments of the present invention have been presented for purposes of illustration and description. The present invention is not intended to be exhaustive or to limit the invention. The exemplary embodiments were chosen and described in order to explain the particular embodiments of the embodiments of the invention The scope of the invention is defined by the appended claims and their equivalents.

 Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The function is implemented in the form of a software functional unit and is produced as an independent product. When the product is sold or used, it can be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to make a computer device (which may be a personal computer, a server, or a network) and the foregoing storage medium includes: a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM). , Random Access Memory ), a variety of media that can store program code, such as a disk or a disc.

Claims

claims 1. A database expansion method, characterized in that the method is applied to a database system including a load balancer and a main database, and the method includes: the load balancer creates a sub-database; and The load balancer sends a first data synchronization instruction to the main database, so that the main database synchronizes the data stored in the main database to the sub-database; Wherein, the main database is a database that allows users to perform data reading and writing operations; the sub-database is a database that only allows users to perform data reading operations. 2. The database expansion method as claimed in claim 1, further comprising: The load balancer receives the data write request; The load balancer sends a data writing instruction to the main database according to the data writing request to write the requested data into the main database; the load balancer sends a second data writing instruction to the main database. Data synchronization instructions, 3. The database expansion method as claimed in claim 1 or 2, further comprising: The load balancer receives the data read request; The load balancer selects a matching database from the main database and the sub-database according to the database system access policy; The load balancer sends a data read instruction to the matching database to read the requested data from the matching database. 4. The database expansion method according to claim 3, wherein the database system access policy includes at least one of a database system access load balancing policy and a database system access speed policy. 5. A database expansion device, characterized in that the database expansion device is applied to a database system including a main database, and the database expansion device includes: Creation unit, used to create sub-databases; A sending unit, configured to send a first data synchronization instruction to the main database, so that the main database synchronizes the data stored in the main database to the sub-database; Wherein, the main database is a database that allows users to perform data reading and writing operations; the sub-database is a database that only allows users to perform data reading operations. 6. The database expansion device according to claim 5, further comprising a receiving unit, The receiving unit is used to receive a data write request; send a data write instruction to the database to write the requested data into the main database, and send a second data synchronization instruction to the main database so that the host 7. The database expansion device according to claim 6, further comprising a selection unit, The receiving unit is also used to receive data reading requests; The selection unit is used to select a matching database from the main database and the sub-database according to the database system access policy; The sending unit is also used to send a data reading instruction to the matching database to read the requested data from the matching database; Wherein, the database system access policy includes at least one of a database system access load balancing policy and a database system access speed policy. 8. A database system, characterized by including a load balancer and a main server database; The load balancer creates a sub-database and sends a first data synchronization instruction to the main database; The main database receives the first data synchronization instruction and synchronizes the data stored in the main database to the sub-database; Wherein, the main database is a database that allows users to perform data reading and writing operations; the sub-database is a database that only allows users to perform data reading operations. 9. The database system according to claim 8, characterized in that: the load balancer receives a data write request, and sends a data write instruction to the main database according to the data write request; The main database receives the data writing instruction and writes the requested data into the main database; The load balancer sends a second data synchronization instruction to the primary database; and The main database receives the second data synchronization instruction and synchronizes the written data to the sub-database. 10. The database system according to claim 8 or 9, characterized in that: the load balancer receives a data read request, selects a matching database from the main database and the sub-database according to the database system access policy, and Send data reading instructions to the matching database; The matching database receives the data reading instruction and provides the requested data according to the data reading instruction; Wherein, the database system access policy includes at least one of a database system access load balancing policy and a database system access speed policy.