CN106021335A - A database accessing method and device - Google Patents

Abstract

The present invention provides a method and device for accessing a database. The method includes: receiving a database access request from a client; performing type analysis on the request to determine whether the request is a data writing request; and when the When the request is a data write request, record the write operation corresponding to the request to the local log, and write the data corresponding to the request into the cache layer of the database. The embodiment of the present invention directly writes the data corresponding to the data writing request into the cache layer of the database, and returns a response message to the client, which can improve the efficiency of subsequent reading of the data.

Description

Method and device for accessing database

technical field

The invention relates to the field of computer technology, in particular to a method and device for accessing a database.

Background technique

With the development of society, a large amount of data needs to be stored, and certain data access methods are used to process the stored data according to the needs of different users. Database is a technology that meets this demand. Simply put, a database is a collection of data stored in a way that can be persisted and manipulated.

In practical applications, users can read and write data in the database, such as adding, deleting, modifying, querying and other operations. In related technologies, the LSM Tree database represented by leveldb is taken as an example. When a user reads hot data in the database, the database will search for it from the local file after receiving the read operation request from the user client. , and then return a response message to the user client. Such a reading method has low reading performance and cannot satisfy the situation where a large number of hot data requests are required. Therefore, it is urgent to solve this technical problem.

Contents of the invention

In view of the above problems, the present invention is proposed to provide a method for accessing a database and a corresponding device that overcome the above problems or at least partially solve the above problems.

According to one aspect of the present invention, a method for accessing a database is provided, including:

Receive a request from the client to access the database;

performing type analysis on the request to determine whether the request is a data writing request; and

When the request is a data write request, record the write operation corresponding to the request to a local log, and write the data corresponding to the request into the cache layer of the database.

Optionally, the method also includes:

When the request is a data read request, the data corresponding to the request is searched in the cache layer, and the found data is returned to the client.

Optionally, the step of recording the corresponding write operation of the request to a local log, and writing the corresponding data of the request into the cache layer of the database further includes:

Invoking the first thread, and using the first thread to record the write operation corresponding to the request to the local log and write the data corresponding to the request into the cache layer.

Optionally, the method also includes:

invoking a second thread and scanning the local log with the second thread to determine whether a log delta exists in the local log, wherein the second thread is asynchronous to the first thread; and

If it is found that there is a log increment in the local log, write the data corresponding to the log increment into the database.

Optionally, the step of using the second thread to scan the local log to determine whether there is a log increment in the local log further includes:

Using the second thread to scan the local log to determine whether there are unmarked log records in the local log; and

If yes, determine that the unmarked log record is the log increment.

Optionally, after writing the data corresponding to the log increment into the database, the method further includes:

Mark the log record corresponding to the log increment in the local log.

Optionally, the method also includes:

Delete marked log records in the local log.

Optionally, the method also includes:

After the database fails and restarts, scan the local log to determine whether there are unmarked log records in the local log; and

If yes, write the corresponding data of the unmarked log record into the database, and mark the unmarked log record in the local log.

Optionally, the method also includes:

When the request is a read request for data, if the data corresponding to the request is not found in the cache layer, forward the request to the database; and

Search the database for data corresponding to the request, return the found data corresponding to the request to the client, and cache the data corresponding to the request in the cache layer.

Optionally, the cache layer is a distributed cache system memcached.

According to another aspect of the present invention, a device for accessing a database is also provided, including:

A request receiving module, adapted to receive a request from a client to access a database;

A request analysis module, adapted to perform type analysis on the request to determine whether the request is a data writing request; and

The first write module is adapted to record the write operation corresponding to the request to a local log and write the data corresponding to the request when the request analyzing module determines that the request is a write request of data The caching layer of the database.

Optionally, the device also includes:

The reading module is adapted to, when the request analysis module determines that the request is a read request for data, search the cache layer for data corresponding to the request, and return the found data to the client.

Optionally, the first writing module is also suitable for:

Invoking the first thread, and using the first thread to record the write operation corresponding to the request to the local log and write the data corresponding to the request into the cache layer.

Optionally, the device also includes:

A second writing module, adapted to call a second thread and utilize the second thread to scan the local log to determine whether there is a log increment in the local log, wherein the second thread is asynchronous to the first thread ; and if it is found that there is a log increment in the local log, writing the data corresponding to the log increment into the database.

Optionally, the second writing module is also suitable for:

Using the second thread to scan the local log to determine whether there are unmarked log records in the local log; and

If yes, determine that the unmarked log record is the log increment.

Optionally, the device also includes:

The marking module is adapted to mark the log record corresponding to the log increment in the local log after the second writing module writes the data corresponding to the log increment into the database.

Optionally, the device also includes:

A deletion module, adapted to delete marked log records in the local log.

Optionally, the device also includes:

The failure processing module is adapted to scan the local log to determine whether there are unmarked log records in the local log after the database fails and restarts; and

If yes, write the corresponding data of the unmarked log record into the database, and mark the unmarked log record in the local log.

Optionally, the reading module is also suitable for:

When the request analysis module determines that the request is a read request for data, if the data corresponding to the request is not found in the cache layer, the request is forwarded to the database; and

Search the database for data corresponding to the request, return the found data corresponding to the request to the client, and cache the data corresponding to the request in the cache layer.

Optionally, the cache layer is a distributed cache system memcached.

In the embodiment of the present invention, when a request from the client for accessing the database is received, type analysis is performed on the request to determine whether the request is a data writing request. When it is determined that the request is a data write request, the write operation corresponding to the data write request is recorded in the local log, and the data corresponding to the data write request is written into the cache layer of the database. It can be seen that the embodiment of the present invention directly writes the data corresponding to the data write request into the cache layer of the database, and returns a response message to the client, which can improve the efficiency of subsequent reading of the data. Moreover, the embodiment of the present invention records the write operation corresponding to the data write request to the local log, so that the data corresponding to the write request can be written into the database asynchronously by using the local log, ensuring the persistence and integrity of the data in the database. In addition, after the database fails and restarts, the local log can also be used to restore the data of the database to achieve the purpose of fault recovery.

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the specific embodiments of the present invention are enumerated below.

Those skilled in the art will be more aware of the above and other objects, advantages and features of the present invention according to the following detailed description of specific embodiments of the present invention in conjunction with the accompanying drawings.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiment. The drawings are only for the purpose of illustrating a preferred embodiment and are not to be considered as limiting the invention. Also throughout the drawings, the same reference numerals are used to designate the same parts. In the attached picture:

FIG. 1 shows a schematic flow diagram of a method for accessing a database according to an embodiment of the present invention;

FIG. 2 shows a schematic flowchart of a method for accessing a database according to another embodiment of the present invention;

FIG. 3 shows a schematic structural diagram of a device for accessing a database according to an embodiment of the present invention; and

Fig. 4 shows a schematic structural diagram of an apparatus for accessing a database according to another embodiment of the present invention.

detailed description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

In order to solve the above technical problem, an embodiment of the present invention provides a method for accessing a database. Fig. 1 shows a schematic flowchart of a method for accessing a database according to an embodiment of the present invention. As shown in Figure 1, the method may at least include step S102, step S104 and step S106:

Step S102, receiving a request from a client to access a database;

Step S104, performing type analysis on the request to determine whether the request is a data writing request;

Step S106, when the request is a data write request, record the write operation corresponding to the request to the local log, and write the data corresponding to the request into the cache layer of the database.

In this step, the local log refers to the log file stored by the database on the hard disk of the local physical machine, which is used to record the operation of the database being accessed.

In the embodiment of the present invention, when a request from the client for accessing the database is received, type analysis is performed on the request to determine whether the request is a data writing request. When it is determined that the request is a data write request, the write operation corresponding to the data write request is recorded in the local log, and the data corresponding to the data write request is written into the cache layer of the database. It can be seen that the embodiment of the present invention directly writes the data corresponding to the data write request into the cache layer of the database, and returns a response message to the client without writing the data into the database, which can improve the subsequent reading of the data. efficiency. Moreover, the embodiment of the present invention records the write operation corresponding to the data write request to the local log, so that the data corresponding to the write request can be written into the database asynchronously by using the local log, ensuring the persistence and integrity of the data in the database. In addition, after the database fails and restarts, the local log can also be used to restore the data of the database to achieve the purpose of fault recovery.

In an optional embodiment of the present invention, in order to improve the security of database access, after receiving the request for accessing the database from the client in step S102 above, the legitimacy of the request can be verified, and subsequent verification can be performed after the verification is passed. In step S104 and step S106, if the verification fails, interception processing is performed and an alarm prompt is issued. The legitimacy here is measured according to the preset security authentication strategy, which may include the legitimacy of the authority, validity of the request, or attack check, etc., and the present invention is not limited thereto. For example, the security authentication policy can be set according to which IP address the client is not allowed to query the database; clients other than a certain IP address cannot delete or modify data in the database, and other policies.

In an optional embodiment of the present invention, when the type analysis is performed on the request in step S104, the statement for accessing the database can be parsed out from the request, and the type of operation of the statement is analyzed to determine whether the request is a data request. write request. The types here are such as add, delete, modify, query, etc. When the statement is a statement of an increase operation, the request is determined to be a data write request; when the statement is a statement of a delete operation, the request is determined to be a data write request ; When the statement is a statement of a modify operation, it is determined that the request is a data write request; when the statement is a statement of a query operation, it is determined that the request is a data read request, and so on.

In an optional embodiment of the present invention, the cache layer mentioned in step S106 above may be a newly created cache layer outside the database. Since the database itself does not have a cache layer, the embodiment of the present invention chooses to create a new cache layer outside the database for temporary storage of data. For example, after the write operation corresponding to the write request is recorded in the local log, the data corresponding to the write request is written into the newly created cache layer, and a response message is returned to the client, thereby improving the subsequent reading of the data. efficiency. Here, a cache layer with corresponding storage capacity can be selected according to business requirements. The type of the cache layer can be, for example, the distributed cache system memcached or the content-based redis.

In an optional embodiment of the present invention, the above step S106 records the write operation corresponding to the request to the local log, and writes the data corresponding to the request into the cache layer of the database. The embodiment of the present invention provides a The selected solution, in this solution, the first thread can be called, and the first thread can be used to record the corresponding write operation of the request to the local log and write the corresponding data of the request into the cache layer. That is to say, the first thread records the write operation corresponding to the request to the local log, then writes the data corresponding to the request into the cache layer, and then returns a response message indicating that the database write has been completed to the client.

Further, in order to ensure the persistence and integrity of the data in the database, the embodiment of the present invention can use the local log to asynchronously write the data corresponding to the write request into the database, that is, call the second thread and use the second thread to scan the local log To determine whether there is a log increment in the local log, wherein the second thread is asynchronous with the first thread, and if it is found that there is a log increment in the local log, then write the corresponding data of the log increment into the database. Here, the second thread may scan the local log in real time, or may scan the local log at a specified scan period (such as 0.5 second or 1 second, etc.).

In an optional embodiment of the present invention, when determining the log increment, the embodiment of the present invention provides an optional solution, that is, using the second thread to scan the local log to determine whether there is an unmarked log in the local log Log records, if there are unmarked log records, determine the unmarked log records as log increments. Further, after the data corresponding to the log increment is written into the database, the log record corresponding to the log increment is marked in the local log to indicate that the data corresponding to the log increment has been written into the database, which can avoid repeated writing The problem. For example, after the data corresponding to the log increment is written into the database, the log record corresponding to the log increment can be marked as "operated" or "recorded" in the local log.

In an optional embodiment of the present invention, in order to save local storage space, marked log records in the local log may be deleted, for example, the local log may be set to delete marked log records at predetermined intervals. In addition, the local log can be split according to the size. When all the log records in a split area have been marked, the log records in the split area can be deleted.

In an optional embodiment of the present invention, if the database fails due to downtime or other factors, so that the data newly written in the cache layer has not been persisted in the database, after the next restart of the database, the local log can be used to Perform data recovery on the database to achieve the purpose of fault repair. Specifically, after the database fails and restarts, enable the scanning thread, and use the scanning thread to scan the local log to determine whether there are unmarked log records in the local log, and if so, write the corresponding data of the unmarked log record to into the database, and mark unmarked log records in the local log. For example, the data "b=2" newly written in the cache layer is not persisted in the database (the corresponding write operation of "b=2" has been recorded in the local log), the database suddenly fails, and after the database is restarted, Enable the scanning thread, and use the scanning thread to scan the local log, and find that there are unmarked log records in the local log, that is, the corresponding write operation of "b=2", then write "b=2" into the database, and locally Unmarked log records (that is, the write operation corresponding to "b=2") are marked in the log, such as marked as "operated" or "recorded".

Furthermore, after the data recovery, the database works normally, and new data is written in the cache layer (here, the first thread mentioned above can be used to record the corresponding write operation of the request to the local log and write the corresponding data of the request In this case, you can continue to use the scanning thread to scan the local log to determine whether there is a log increment in the local log. If you find that there is a log increment in the local log, write the corresponding data of the log increment into the database. The scanning thread here has the same function as the second thread mentioned above, and the scanning thread is asynchronous to the first thread.

In an optional embodiment of the present invention, since the data is cached at the cache layer, when the request from the client for accessing the database is a read request for data, the corresponding data of the read request can be directly searched in the cache layer. , and return the found data to the client, thereby reducing the reading access to the database and improving the efficiency of data reading.

In an optional embodiment of the present invention, if a database failure or other factors cause some or all of the data in the cache layer to be lost, so that the data corresponding to the read request cannot be found in the cache layer, the embodiment of the present invention can send the read request to Forward to the database, find the data corresponding to the read request in the database, return the found data corresponding to the read request to the client, and cache the data corresponding to the read request in the cache layer.

The implementation process of the method for accessing the database of the present invention will be introduced in detail below through a specific embodiment. In this embodiment, a cache layer with a corresponding storage capacity is selected according to business requirements, and a new cache layer is created for the database. The type of the cache layer can be, for example, a distributed cache system memcached or a memory-based redis.

Fig. 2 shows a schematic flowchart of a method for accessing a database according to another embodiment of the present invention. As shown in FIG. 2, the method may at least include step S202, step S204, step S206, step S208 and step S210.

Step S202, creating a cache layer for the database, and receiving a request from a client to access the database.

Step S204, analyze the type of the request to determine whether the request is a data write request, if yes, proceed to step S206; if not, proceed to step S208.

Step S206, call the first thread, and use the first thread to record the write operation corresponding to the request to the local log and write the data corresponding to the request into the cache layer.

In this step, the local log refers to the log file stored by the database on the hard disk of the local physical machine, which is used to record the operation of the database being accessed.

Step S208, when the request from the client to access the database is a data read request, search the cache layer for data corresponding to the read request, and return the found data to the client.

In this step, if the data in the cache layer is partially or completely lost due to database failure or other factors, so that the data corresponding to the read request cannot be found in the cache layer, the embodiment of the present invention may forward the read request to the database, and then Find the data corresponding to the read request in the database, return the found data corresponding to the read request to the client, and cache the data corresponding to the read request in the cache layer.

Step S210, calling the second thread and using the second thread to scan the local log to determine whether there is a log increment in the local log, wherein the second thread is asynchronous with the first thread, and if it is found that there is a log increment in the local log, then the log is incremented. The corresponding amount of data is written into the database.

When determining the log increment, the second thread can be used to scan the local log to determine whether there is an unmarked log record in the local log, and if there is an unmarked log record, then determine that the unmarked log record is the log increment . Further, after the data corresponding to the log increment is written into the database, the log record corresponding to the log increment is marked in the local log to indicate that the data corresponding to the log increment has been written into the database, which can avoid repeated writing The problem. For example, after the data corresponding to the log increment is written into the database, the log record corresponding to the log increment can be marked as "operated" or "recorded" in the local log. In addition, in order to save local storage space, marked log records in the local log can be deleted.

In the embodiment of the present invention, if the database fails due to downtime or other factors, so that the data newly written in the cache layer has not been persisted in the database, after the next restart of the database, the local log can be used to update the database. Data recovery, to achieve the purpose of fault repair. Specifically, after the database fails and restarts, enable the scanning thread, and use the scanning thread to scan the local log to determine whether there are unmarked log records in the local log, and if so, write the corresponding data of the unmarked log record to into the database, and mark unmarked log records in the local log.

Furthermore, after the data recovery, the database works normally, and new data is written in the cache layer (here, the first thread mentioned above can be used to record the corresponding write operation of the request to the local log and write the corresponding data of the request In this case, you can continue to use the scanning thread to scan the local log to determine whether there is a log increment in the local log. If you find that there is a log increment in the local log, write the corresponding data of the log increment into the database. The scanning thread here has the same function as the second thread mentioned above, and the scanning thread is asynchronous to the first thread.

It should be noted that, in practical applications, all the above optional implementation manners may be combined arbitrarily in combination to form optional embodiments of the present invention, which will not be repeated here.

Based on the method for accessing a database provided in the above embodiments and based on the same inventive concept, an embodiment of the present invention also provides a device for accessing a database.

Fig. 3 shows a schematic structural diagram of an apparatus for accessing a database according to an embodiment of the present invention. As shown in FIG. 3 , the apparatus 300 may at least include a request receiving module 310 , a request analyzing module 320 and a first writing module 330 .

Now introduce the functions of each component or device of the apparatus 300 for accessing the database in the embodiment of the present invention and the connection relationship between each part:

A request receiving module 310, adapted to receive a request from a client to access a database;

The request analysis module 320, coupled with the request receiving module 310, is adapted to perform type analysis on the request to determine whether the request is a data writing request; and

The first write module 330, coupled with the request analysis module 320, is adapted to record the corresponding write operation of the request to the local log when the request analysis module determines that the request is a write request of data, and write the corresponding data of the request to into the cache layer of the database.

In an embodiment of the present invention, as shown in FIG. 4, the device shown in FIG. 3 may further include:

The reading module 340, coupled with the request analyzing module 320 and the first writing module 330, is suitable for searching the corresponding data in the cache layer when the request analyzing module 320 determines that the request is a read request of data, and will search The received data is returned to the client.

In an embodiment of the present invention, the first writing module 330 is also suitable for:

The first thread is called, and the first thread is used to record the corresponding write operation of the request to the local log and write the corresponding data of the request to the cache layer.

In an embodiment of the present invention, as shown in FIG. 4, the device shown in FIG. 3 may further include:

The second write module 350, coupled with the first write module 330, is adapted to call the second thread and utilize the second thread to scan the local log to determine whether there is a log increment in the local log, wherein the second thread and the first thread Asynchronous; and if it is found that there is a log increment in the local log, write the corresponding data of the log increment into the database.

In an embodiment of the present invention, the second writing module 350 is also suitable for:

Utilize the second thread to scan the local log to determine whether there are unmarked log records in the local log; and

If so, it is determined that unmarked log records are log increments.

In an embodiment of the present invention, as shown in FIG. 4, the device shown in FIG. 3 may further include:

The marking module 360, coupled with the second writing module 350, is adapted to mark the log record corresponding to the log increment in the local log after the second writing module 350 writes the data corresponding to the log increment into the database .

In an embodiment of the present invention, as shown in FIG. 4, the device shown in FIG. 3 may further include:

The deletion module 370, coupled with the marking module 360, is adapted to delete the marked log records in the local log.

In an embodiment of the present invention, as shown in FIG. 4, the device shown in FIG. 3 may further include:

The failure processing module 380, coupled with the first writing module 330 and the marking module 360, is adapted to scan the local log after the database fails and restarts, and determines whether there are unmarked log records in the local log; and

If so, write the corresponding data of the unmarked log records into the database, and mark the unmarked log records in the local log.

In an embodiment of the present invention, the reading module 340 is also suitable for:

When the request analysis module determines that the request is a read request for data, if the data corresponding to the request is not found in the cache layer, the request is forwarded to the database;

Find the data corresponding to the request in the database, return the found data corresponding to the request to the client, and cache the corresponding data in the cache layer.

In an embodiment of the present invention, the cache layer is a distributed cache system memcached.

According to any one of the above preferred embodiments or a combination of multiple preferred embodiments, the embodiments of the present invention can achieve the following beneficial effects:

In the embodiment of the present invention, when a request from the client for accessing the database is received, type analysis is performed on the request to determine whether the request is a data writing request. When it is determined that the request is a data write request, the write operation corresponding to the data write request is recorded in the local log, and the data corresponding to the data write request is written into the cache layer of the database. It can be seen that the embodiment of the present invention directly writes the data corresponding to the data write request into the cache layer of the database, and returns a response message to the client, which can improve the efficiency of subsequent reading of the data. Moreover, the embodiment of the present invention records the write operation corresponding to the data write request to the local log, so that the data corresponding to the write request can be written into the database asynchronously by using the local log, ensuring the persistence and integrity of the data in the database. In addition, after the database fails and restarts, the local log can also be used to restore the data of the database to achieve the purpose of fault recovery.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, in order to streamline this disclosure and to facilitate an understanding of one or more of the various inventive aspects, various features of the invention are sometimes grouped together in a single embodiment, figure, or its description. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art can understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method or method so disclosed may be used in any combination, except that at least some of such features and/or processes or units are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will understand that although some embodiments described herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the invention. and form different embodiments. For example, in the claims, any one of the claimed embodiments can be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all functions of some or all components in the apparatus for accessing a database according to the embodiment of the present invention. The present invention can also be implemented as an apparatus or an apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program for realizing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet site, or provided on a carrier signal, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. does not indicate any order. These words can be interpreted as names.

So far, those skilled in the art should appreciate that, although a number of exemplary embodiments of the present invention have been shown and described in detail herein, without departing from the spirit and scope of the present invention, the disclosed embodiments of the present invention can still be used. Many other variations or modifications consistent with the principles of the invention are directly identified or derived from the content. Accordingly, the scope of the present invention should be understood and deemed to cover all such other variations or modifications.

One aspect of the embodiments of the present invention discloses A1, a method for accessing a database, including:

Receive a request from the client to access the database;

performing type analysis on the request to determine whether the request is a data writing request; and

When the request is a data write request, record the write operation corresponding to the request to a local log, and write the data corresponding to the request into the cache layer of the database.

A2. The method according to A1, which also includes:

When the request is a data read request, the data corresponding to the request is searched in the cache layer, and the found data is returned to the client.

A3. The method according to A1 or A2, wherein the step of recording the corresponding write operation of the request to a local log, and writing the corresponding data of the request into the cache layer of the database further includes:

Invoking the first thread, and using the first thread to record the write operation corresponding to the request to the local log and write the data corresponding to the request into the cache layer.

A4. The method according to any one of A1-A3, further comprising:

invoking a second thread and scanning the local log with the second thread to determine whether a log delta exists in the local log, wherein the second thread is asynchronous to the first thread; and

If it is found that there is a log increment in the local log, write the data corresponding to the log increment into the database.

A5. The method according to any one of A1-A4, wherein the step of using the second thread to scan the local log to determine whether there is a log increment in the local log further includes:

Using the second thread to scan the local log to determine whether there are unmarked log records in the local log; and

If yes, determine that the unmarked log record is the log increment.

A6. The method according to any one of A1-A5, wherein, after writing the data corresponding to the log increment into the database, the method further includes:

Mark the log record corresponding to the log increment in the local log.

A7. The method according to any one of A1-A6, further comprising:

Delete marked log records in the local log.

A8. The method according to any one of A1-A7, further comprising:

After the database fails and restarts, scan the local log to determine whether there are unmarked log records in the local log; and

If yes, write the corresponding data of the unmarked log record into the database, and mark the unmarked log record in the local log.

A9. The method according to any one of A1-A8, further comprising:

When the request is a read request for data, if the data corresponding to the request is not found in the cache layer, forward the request to the database; and

Search the database for data corresponding to the request, return the found data corresponding to the request to the client, and cache the data corresponding to the request in the cache layer.

A10. The method according to any one of A1-A9, wherein the cache layer is a distributed cache system memcached.

Another aspect of the embodiments of the present invention also discloses B11, a device for accessing a database, including:

A request receiving module, adapted to receive a request from a client to access a database;

A request analysis module, adapted to perform type analysis on the request to determine whether the request is a data writing request; and

The first write module is adapted to record the write operation corresponding to the request to a local log and write the data corresponding to the request when the request analyzing module determines that the request is a write request of data The caching layer of the database.

B12. The device according to B11, further comprising:

The reading module is adapted to, when the request analysis module determines that the request is a read request for data, search the cache layer for data corresponding to the request, and return the found data to the client.

B13. The device according to B11 or B12, wherein the first writing module is further adapted to:

Invoking the first thread, and using the first thread to record the write operation corresponding to the request to the local log and write the data corresponding to the request into the cache layer.

B14. The device according to any one of B11-B13, further comprising:

A second writing module, adapted to call a second thread and utilize the second thread to scan the local log to determine whether there is a log increment in the local log, wherein the second thread is asynchronous to the first thread ; and if it is found that there is a log increment in the local log, writing the data corresponding to the log increment into the database.

B15. The device according to any one of B11-B14, wherein the second writing module is further adapted to:

Using the second thread to scan the local log to determine whether there are unmarked log records in the local log; and

If yes, determine that the unmarked log record is the log increment.

B16. The device according to any one of B11-B15, further comprising:

The marking module is adapted to mark the log record corresponding to the log increment in the local log after the second writing module writes the data corresponding to the log increment into the database.

B17. The device according to any one of B11-B16, further comprising:

A deletion module, adapted to delete marked log records in the local log.

B18. The device according to any one of B11-B17, further comprising:

The failure processing module is adapted to scan the local log to determine whether there are unmarked log records in the local log after the database fails and restarts; and

If yes, write the corresponding data of the unmarked log record into the database, and mark the unmarked log record in the local log.

B19. The device according to any one of B11-B18, wherein the reading module is further adapted to:

When the request analysis module determines that the request is a read request for data, if the data corresponding to the request is not found in the cache layer, the request is forwarded to the database; and

Search the database for data corresponding to the request, return the found data corresponding to the request to the client, and cache the data corresponding to the request in the cache layer.

B20. The device according to any one of B11-B19, wherein the cache layer is a distributed cache system memcached.

Claims (10)

1. A method for accessing a database, comprising: Receive a request from the client to access the database; performing type analysis on the request to determine whether the request is a data writing request; and When the request is a data write request, record the write operation corresponding to the request to a local log, and write the data corresponding to the request into the cache layer of the database. 2. The method of claim 1, further comprising: When the request is a data read request, the data corresponding to the request is searched in the cache layer, and the found data is returned to the client. 3. The method according to claim 1 or 2, wherein the step of recording the corresponding write operation of the request to a local log, and writing the corresponding data of the request into the cache layer of the database is further include: Invoking the first thread, and using the first thread to record the write operation corresponding to the request to the local log and write the data corresponding to the request into the cache layer. 4. The method according to any one of claims 1-3, further comprising: invoking a second thread and scanning the local log with the second thread to determine whether a log delta exists in the local log, wherein the second thread is asynchronous to the first thread; and If it is found that there is a log increment in the local log, write the data corresponding to the log increment into the database. 5. The method according to any one of claims 1-4, wherein said step of utilizing said second thread to scan said local log to determine whether there is a log increment in said local log further comprises: Using the second thread to scan the local log to determine whether there are unmarked log records in the local log; and If yes, determine that the unmarked log record is the log increment. 6. The method according to any one of claims 1-5, wherein, after writing the data corresponding to the log increment into the database, the method further comprises: Mark the log record corresponding to the log increment in the local log. 7. The method according to any one of claims 1-6, further comprising: Delete marked log records in the local log. 8. The method according to any one of claims 1-7, further comprising: After the database fails and restarts, scan the local log to determine whether there are unmarked log records in the local log; and If yes, write the corresponding data of the unmarked log record into the database, and mark the unmarked log record in the local log. 9. The method according to any one of claims 1-8, further comprising: When the request is a read request for data, if the data corresponding to the request is not found in the cache layer, forward the request to the database; and Search the database for data corresponding to the request, return the found data corresponding to the request to the client, and cache the data corresponding to the request in the cache layer. 10. A device for accessing a database, comprising: A request receiving module, adapted to receive a request from a client to access a database; A request analysis module, adapted to perform type analysis on the request to determine whether the request is a data writing request; and The first write module is adapted to record the write operation corresponding to the request to a local log and write the data corresponding to the request when the request analyzing module determines that the request is a write request of data The caching layer of the database.