Database read-write separating method and device

Abstract

The invention discloses a database read-write separating method and a database read-write separating device. The method comprises the following steps of: defining and accessing a naming mode of a service method of a write database, and naming the service method according to the defined naming mode; judging whether the service method is a method for accessing the write database according to the name of the service method and the defined naming mode when the database is required to be accessed through the service method; positioning to the write database if the service method is the method for accessing the write database, otherwise, positioning the service method to a read database. By the method, the database read-write is separated by judging the name of the service method.

Description

technical field [0001] The invention relates to the field of database access, in particular to a method and device for separating reading and writing of a database. Background technique [0002] With the development of the Internet, the application of large databases has become an indispensable part of web applications. Usually, we use a database for read and write operations. This technical solution will make database access a bottleneck in large concurrent access, so Database reading and writing separation technology emerged as the times require, which separates database reading and writing, which can effectively solve the pressure in the case of large database concurrency. figure 1 It is a schematic diagram of database reading and writing separation in the prior art. [0003] Such as figure 1 As shown, a read-write library (Master) and multiple read-write libraries (Slave) are usually set up in a group of databases. Access the Slave library when performing read operati...

AI Technical Summary

Problems solved by technology

[0004] As for how to quickly and effectively access the Master library or the Slave library according to different businesses, the basic solution in the traditional solution is to hard-code it into the program, and rely on the programmer's thinking to distinguish between read operations and write operations. This method produces a large number of Repeated codes lead to very high coupling between business logic and read and write operations, and the more business codes, the more error-prone

Images