Method and system for read-write splitting database

Abstract

The invention discloses a method and a system for a read-write splitting database. The system comprises an application server layer, a database access interface layer, a database agent layer and a database layer. The database agent layer is arranged between the database access interface layer and the database layer to conduct data communication, switch data sources and provide route service, data definition language (DDL) statement analysis, database state monitoring, high availability, data source switching and transaction control service. The method and the system achieve the aim that read-write splitting can be conducted between any database software and versions by conducting read-write splitting on a business layer.

Description

technical field [0001] The invention relates to the field of network communication, in particular to a method and system for separating read and write databases. Background technique [0002] With the development of the Internet, the business of each website continues to expand, the data continues to increase, the pressure on the database is increasing, and the reading and writing mechanism of the database is becoming more and more important. pressure. [0003] The basic principle of Read / Write Splitting in the traditional sense is to let the master database (master) handle transactional queries, while the slave database (slave) handles SELECT queries, and database replication is used to Changes are synchronized to the slave database in the cluster. For websites with a large number of visits, read-write separation is generally used. For example, the read-write ratio of eBay is 260:1. [0004] figure 1 It is a schematic diagram of the traditional MySQL read-write separatio...

AI Technical Summary

Problems solved by technology

The disadvantages of this scheme are: 1) The transaction support is poor, because the phenomenon of transaction interference will occur when the write operation is performed on the agent side, if you want to support the transaction, you must use at least two connection pools on the business logic side, and one connection pool is responsible for The end reads data, and another connection pool is responsible for directly writing data on the database, which is very complicated in the coding process; 2) It must be implemented between the same database software, such as only MySQL and the same version Read and write separation can only be done between software, poor compatibility

Images