Database read-write separation method and platform

Abstract

The invention belongs to the technical field of database data processing, and particularly relates to a database read-write separation method which comprises the following steps: a user sends a gateway service request to a gateway through a client application; after the gateway receives the gateway service request, the read-only information of the service is loaded from the gateway service cache, and the read-only attribute of the service is judged; if the gateway service is a write service, the background micro-service cluster sends the service to a main database, and the main database executes a write operation according to the service, receives a write response returned by the main database, and returns the write response to the client through the gateway; and if the gateway service is the read-only service, dynamically switching the background micro-service cluster, sending the service to the slave database, receiving a read-only response returned by the slave database, and returning the read-only response to the client through the gateway. The defects in the prior art are overcome, the gateway service is judged and marked, and read-only and write are separated to the slave database and the master database.

Description

technical field [0001] The invention belongs to the technical field of database data processing, and in particular relates to a database reading and writing separation method and platform. Background technique [0002] Since all read and write operations fall on the main database, as the number of users of the platform increases, the pressure on the database gradually increases, so it is decided to implement read and write separation. [0003] Regarding the read-write separation scheme, the most commonly used ones in the industry are as follows: [0004] Solution 1: The application judges according to the business logic, sends write operation commands such as adding, deleting, and modifying to the main database, and sends query commands to the standby database. [0005] Solution 2: Use middleware as a proxy, responsible for identifying whether to read or write database requests, and distribute them to different databases. [0006] Common middleware: [0007] <1>MySQ...

AI Technical Summary

Problems solved by technology

In a distributed scenario, due to the complexity of calling links between services, in an existing huge business system, the above two solutions cannot solve the problem of delay in reading immediately after writing, so it is not possible to automatically read all services Write separation, otherwise some online problems will occur

Images