WO2023050706A1

WO2023050706A1 - Database multi-write method and apparatus, and related device

Info

Publication number: WO2023050706A1
Application number: PCT/CN2022/078209
Authority: WO
Inventors: 董善义
Original assignee: 苏州浪潮智能科技有限公司
Priority date: 2021-09-30
Filing date: 2022-02-28
Publication date: 2023-04-06
Also published as: CN113590595A

Abstract

Disclosed in the present application is a database multi-write method. The method comprises: when a first database cluster receives a write instruction, an Envoy proxy deployed in the first database cluster intercepting the write instruction; according to the write instruction, determining data to be written; and establishing a connection with a second database cluster according to pre-stored second database cluster information, and writing said data into the second database cluster. By means of the database multi-write method, non-intrusive and automatic database multi-write of a code is realized, thereby improving the database multi-write efficiency, and also reducing the research and development cost. Further disclosed in the present application are a database multi-write apparatus and system and a computer-readable storage medium, which all have the above beneficial effects.

Description

A database multi-write method, device and related equipment

This application claims the priority of the Chinese patent application submitted to the China Patent Office on September 30, 2021, with the application number 202111156691.0, and the title of the invention is "a database multi-writing method, device and related equipment", the entire content of which is incorporated by reference in this application.

technical field

The present application relates to the technical field of databases, in particular to a database multi-writing method, and also relates to a database multi-writing device, system and computer-readable storage medium.

Background technique

In the era of cloud computing, a large number of microservice applications are deployed on the cloud platform, and there are a large number of situations that need to be written to two or more database clusters at the same time, such as business migration, database upgrade, and active and standby databases. At present, developers often write sql (Structured Query Language, Structured Query Language) in another database cluster while writing to one database cluster by modifying the code, so that two or more databases can be kept Data Consistency. However, these operations often have a huge workload, resulting in high research and development costs and low work efficiency.

Therefore, how to realize fast and efficient multi-writing of the database is an urgent problem to be solved by those skilled in the art.

Contents of the invention

The purpose of this application is to provide a method for database multi-writing, which realizes code non-invasive, automatic database multi-writing, improves the efficiency of database multi-writing, and reduces research and development costs; another purpose of this application It provides a database multi-writing device, system and computer-readable storage medium, all of which have the above-mentioned beneficial effects.

In the first aspect, the present application provides a method for multiple database writing, including:

When the first database cluster receives the write command, the Envoy agent deployed in the first database cluster intercepts the write command;

determining data to be written according to the write instruction;

Establishing a connection with the second database cluster according to the pre-stored second database cluster information, and writing the data to be written into the second database cluster.

Optionally, before determining the data to be written according to the write instruction, the method further includes:

Analyzing the write command to obtain a traffic protocol;

Judging whether the traffic protocol conforms to the database communication protocol;

If the traffic protocol conforms to the database communication protocol, the step of determining the data to be written according to the write instruction is executed.

Optionally, the database multi-writing method also includes:

When the first database cluster receives a read instruction, obtain response information corresponding to the read instruction;

determining whether the read operation is successful according to the response information;

If the read operation is unsuccessful, forward the read instruction to the second database cluster;

Acquiring the read data fed back by the second database cluster according to the read instruction;

Feedback the read data to the originator of the read command.

Optionally, before obtaining the response information corresponding to the read instruction, it also includes:

Analyzing the read command to obtain a traffic protocol;

If the traffic protocol conforms to the database communication protocol, the step of acquiring the response information corresponding to the read command is performed.

Optionally, the database multi-writing method also includes:

When the read data fed back by the second data cluster is not obtained, an alarm prompt is output.

Optionally, the Envoy proxy is deployed in each database cluster, and the Envoy proxy in each database cluster is created through service grid technology and Wasm technology.

Optionally, the establishing a connection with the second database cluster according to the pre-stored second database cluster information includes:

Establishing a connection with the second database cluster according to the pre-stored address information of the second database cluster.

In the second aspect, the present application also discloses a database multi-writing device, including:

An instruction interception module, configured to intercept the write instruction by an Envoy agent deployed in the first database cluster when the first database cluster receives the write instruction;

A data determination module, configured to determine the data to be written according to the write instruction;

The data multi-writing module is configured to establish a connection with the second database cluster according to the pre-stored second database cluster information, and write the data to be written into the second database cluster.

In the third aspect, the present application also discloses a database multi-write device, including:

memory for storing computer programs;

A processor, configured to implement the steps of any one of the database multi-writing methods described above when executing the computer program.

In the fourth aspect, the present application also discloses a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, any of the above-mentioned database multi-write method steps.

A database multi-write method provided by the present application includes that when the first database cluster receives a write command, the Envoy agent deployed in the first database cluster intercepts the write command; according to the write command Determine the data to be written; establish a connection with the second database cluster according to the prestored information of the second database cluster, and write the data to be written into the second database cluster.

It can be seen that the database multi-write method provided by this application deploys the Envoy agent in each database cluster, and sets the relevant information of the standby database cluster corresponding to its own database cluster in the Envoy agent, so as to establish a connection with the standby database cluster based on this information. On this basis, the Envoy agent intercepts the data writing instructions received by its own database cluster, and after obtaining the data to be written, writes it to the standby database cluster, thereby realizing database reading and writing. Obviously, this implementation method can realize automatic database multi-writing without code modification, effectively improves the efficiency of database multi-writing, and reduces research and development costs at the same time.

A database multi-writing device, system, and computer-readable storage medium provided by the present application all have the above-mentioned beneficial effects, and will not be repeated here.

Description of drawings

In order to illustrate the prior art and the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the drawings that need to be used in the description of the prior art and the embodiments of the present application. Of course, the following drawings related to the embodiments of the application describe only a part of the embodiments of the application, and those of ordinary skill in the art can obtain other The accompanying drawings, and other obtained drawings also belong to the protection scope of the present application.

Fig. 1 is a schematic flow chart of a database multi-writing method provided by the present application;

Fig. 2 is the implementation flowchart of a kind of database multi-writing and disaster recovery method provided by the application;

Fig. 3 is a schematic structural diagram of a database multi-writing device provided by the present application;

Fig. 4 is a schematic structural diagram of a database multi-writing system provided by the present application;

FIG. 5 is a schematic structural diagram of a computer-readable storage medium provided by the present application.

Detailed ways

The core of this application is to provide a database multi-writing method, the database multi-writing method realizes code non-invasive, automatic database multi-writing, improves the efficiency of database multi-writing, and reduces research and development costs; another core of this application It provides a database multi-writing device, system and computer-readable storage medium, which also have the above-mentioned beneficial effects.

In order to describe the technical solutions in the embodiments of the present application more clearly and completely, the technical solutions in the embodiments of the present application will be introduced below in conjunction with the drawings in the embodiments of the present application. Apparently, the described embodiments are only some of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

The embodiment of the present application provides a database multi-writing method.

Please refer to Fig. 1, Fig. 1 is a schematic flow chart of a method for multi-writing database provided by the present application, the method for multi-writing database may include:

S101: When the first database cluster receives a write command, the Envoy agent deployed in the first database cluster intercepts the write command;

This step aims to intercept the write command, which is the command that needs to write/store data to the corresponding database cluster, and is generally initiated by the client to the database cluster so that the data to be written can be stored in the database cluster. Database cluster. Among them, the interception operation can be implemented by the Envoy agent deployed in the database cluster. Envoy is a self-organizing module designed for the L7 agent and communication bus of the service architecture, and has no direct dependence on the application server. In the specific implementation process, when a database cluster (such as the first database cluster above) receives a write command initiated by the client, the Envoy agent deployed on the database cluster will intercept the command in order to use the write command Perform follow-up operations to achieve multiple writes to the database.

It should be noted that the Envoy agent intercepts the write command to store the data to be written to other database clusters at the same time based on the write command (here, generally, the standby database cluster of the current database cluster, that is, the standby database cluster of the first database cluster , that is, the second database cluster described below), however, it does not affect the data storage operation performed by the first database cluster based on the write instruction.

As an optional embodiment, the above-mentioned Envoy agents are deployed in each database cluster, and the Envoy agents in each database cluster are created through Service Mesh technology and Wasm technology.

This optional embodiment provides a method for deploying an Envoy proxy, which is implemented through service grid technology and Wasm technology, wherein the service grid technology is used to implement data communication between Envoys, and Wasm technology is used to implement function settings and extensions. Specifically, Envoy agents are deployed in each database cluster through service grid technology and Wasm technology, so that all Envoys build a transparent service grid, and the applications in it only need to simply send and receive with the local Envoy information, does not need to focus on the entire network topology.

Among them, the service mesh is the infrastructure layer that handles the communication between services. It is responsible for reliably delivering requests through the complex service topology that constitutes modern cloud-native applications. In practice, Service Mesh is usually in the form of an array of lightweight network agents To implement, these agents are deployed together with the application code, and the application does not need to be aware of the existence of the agent.

Among them, Wasm technology supports technicians to write machine code to run in the browser's virtual security sandbox, and even the upgraded Wasm is designed as a compilation target for other languages, allowing server-side code (such as C or C++ code, etc.) to be compiled In it, it can be combined with the service grid to expand its capabilities.

S102: Determine the data to be written according to the write instruction;

This step aims to realize the determination of the data to be written based on the write instruction. It can be understood that the client that initiates the write command can attach the data to be written to the write command, so that the Envoy proxy can obtain the data to be written by parsing the write command; of course, the client can also You can first initiate a write command to the first database cluster to inform the first database cluster to receive and store the data to be written, and then send the data to be written to the first database cluster, so that the Envoy agent can intercept the write After the command is executed, the data to be written sent to the first database cluster is acquired. It can be seen that the acquisition method of the data to be written is not unique, which is not limited in this application.

As an optional embodiment, before determining the data to be written according to the write instruction, it may also include: parsing the write instruction to obtain the traffic protocol; judging whether the traffic protocol conforms to the database communication protocol; if the traffic protocol conforms to the database communication protocol, execute the step of determining the data to be written according to the write instruction.

The data multi-write method provided by this optional embodiment can determine whether to continue to perform the database multi-write operation by judging whether the write command conforms to the database communication protocol, thereby avoiding the database multi-write due to the write command not conforming to the database communication protocol In case of failure, save resource usage and time wastage. Specifically, when the Envoy agent intercepts a write command, it first parses it to obtain its corresponding traffic protocol, and then judges whether the traffic protocol conforms to the database communication protocol. If the traffic protocol does not conform to the database communication protocol, it no longer Execute the multi-write operation of the database, just discard the write command; if the traffic protocol conforms to the database communication protocol, then perform the step of obtaining the data to be written based on the write command, so as to realize the multi-write function of the database.

S103: Establish a connection with the second database cluster according to the pre-stored second database cluster information, and write the data to be written into the second database cluster.

This step aims to write the data to be written into the second database cluster, which is the standby database cluster of the first database cluster. Of course, the number of the second database clusters can be multiple, that is, the standby database cluster The number of can be multiple, so as to realize multiple backups of the data to be written. In addition, the first database cluster and the second database cluster can be mutually standby database clusters, that is, through the Envoy agent in the first database cluster, the data information written in the first database cluster can be written into the second database cluster at the same time, through the second database cluster The Envoy proxy of the second database cluster can simultaneously write the data information written into the second database cluster into the first database cluster.

Specifically, in the Envoy agent of each database cluster, relevant information of its corresponding standby database cluster is preset, so as to establish a connection with the standby database cluster, thereby realizing the multi-write function of the database. That is to say, the Envoy agent deployed in the first database cluster pre-stores the relevant information of the second database cluster, that is, the above-mentioned pre-stored information of the second database cluster. Therefore, after obtaining the data to be written, it can be based on the pre-stored first The information of the second database cluster establishes a connection with the second database cluster, so that the data to be written is written into the second database cluster. So far, the multi-write operation of the database is completed.

As an optional embodiment, the above-mentioned establishing a connection with the second database cluster according to the pre-stored second database cluster information may include: establishing a connection with the second database cluster according to the pre-stored address information of the second database cluster.

This optional embodiment provides a method for establishing a connection to a database cluster, which is implemented based on the address information of the database cluster, that is, the address information of the standby database cluster (such as the address information of the second database cluster pre-stored above) is stored in the Envoy agent in advance In this way, the Envoy agent deployed in the first database cluster can establish a connection with the second database according to the pre-stored address information of the second database cluster, thereby realizing multiple writes to the database.

As an optional embodiment, the database multi-write method may further include: when the first database cluster receives a read instruction, obtaining response information corresponding to the read instruction; determining whether the read operation is successful according to the response information; if the read If the fetch operation is unsuccessful, the read instruction is forwarded to the second database cluster; the read data fed back by the second database cluster according to the read instruction is obtained; and the read data is fed back to the initiator of the read instruction.

The database multi-write method provided by this optional embodiment can also implement read command interception, so that when the first database cluster fails to return to read data, it can read data from the second database cluster and return to the original read command. Instruction-fetching client, so as to realize the database backup disaster recovery function.

Specifically, when the client needs to read data from the first database cluster, it can initiate a read command to the first database cluster. At this time, the Envoy agent deployed on the first database cluster will also intercept the read command. And obtain the response information of the first database cluster to the read command; further, judge whether the read operation is successful according to the response information, that is, judge whether the first database cluster successfully feeds back the read data to the client, if the read operation is successful, That is, if the first database cluster successfully feeds back the read data to the client, there is no need to perform other operations, and the read command can be discarded. On the contrary, if the read operation of the first database cluster fails, the read command can be sent to The second database cluster, so as to read the target data from the second database cluster, and return the read data to the client.

As an optional embodiment, before obtaining the response information corresponding to the read instruction, it may also include: parsing the read instruction to obtain the traffic protocol; judging whether the traffic protocol conforms to the database communication protocol; if the traffic protocol conforms to the database communication protocol , then execute the step of obtaining the response information corresponding to the read command.

As mentioned above, it is possible to determine whether to continue to perform multiple database write operations by judging whether the write command conforms to the database communication protocol, thereby avoiding the failure of database multiple write operations due to the write command not conforming to the database communication protocol, saving resource usage and time waste. Based on this, it is also possible to determine whether to execute the data read operation for the second database cluster by judging whether the read command conforms to the database communication protocol, thereby avoiding the inability to read data from the second database cluster due to the read command not conforming to the database communication protocol. The situation of fetching data saves resource occupation and time waste. Specifically, when the Envoy agent intercepts a read command, it first parses it to obtain its corresponding traffic protocol, and then judges whether the traffic protocol conforms to the database communication protocol. If the traffic protocol does not conform to the database communication protocol, it no longer Go to the second database cluster to read data, just discard the write command; if the traffic protocol conforms to the database communication protocol, then execute the step of reading data from the second database cluster based on the read command.

As an optional embodiment, the database multi-writing method may further include: when the read data fed back by the second data cluster is not obtained, outputting an alarm prompt.

The database multi-writing method provided in this optional embodiment can also implement an alarm function. Specifically, when the first database cluster cannot feed back the read data to the client, and the Envoy agent of the first database cluster cannot obtain the read data from the second database cluster, it means that the first database cluster and the second database cluster At this time, an alarm prompt can be output to inform the technicians that the current database cluster is abnormal, so that the technicians can trace the source of the exception and maintain it in time.

Based on the above embodiments, the embodiment of the present application provides another database multi-writing method.

Specifically, in the database multi-write method provided by this application, an Envoy agent is deployed on each instance of the database cluster (which can be a pod or a virtual machine or a physical machine), and then the Envoy agent is configured to realize the writing to the database cluster A. Data is written to database cluster B at the same time; at the same time, if an exception or timeout occurs when querying the primary database, traffic can be automatically redirected to the backup database cluster.

First, the deployment and configuration process of the Envoy agent in the database cluster is as follows:

1. Use the service grid technology to create an Envoy proxy for the database cluster instance, so as to use the traffic hijacking capability of the Envoy proxy to hijack the request traffic for the database cluster to the Envoy proxy. The Envoy proxy has the ability to unpack the traffic, The ability to process and repacket.

2. Configure the function of parsing the database communication protocol (currently the mysql protocol is mainly supported). After the Envoy agent captures the tcp connection, according to the first 4 bytes in the Handshake packet (the initialization packet sent by the Server to the Client), you can Identify whether the traffic packet is the traffic of the database, and, according to the traffic of the execution command sent by the subsequent client to the server, the corresponding sql command can be obtained. Thus, by parsing the captured response information of the database cluster, it can be identified whether the command is executed successfully. If the command fails to be executed, the same sql command will be forwarded to the backup database cluster by default.

3. The above-mentioned database communication protocol analysis process can be realized by writing c++ code, and then applying Wasm technology to make a filter (filter) in the form of Wasm and add it to the Envoy proxy to make the interception and analysis process of database traffic into the Envoy agent, so that it does not have The Envoy proxy for related functions has the ability to parse database traffic. In addition, using istio, the control plane of the service grid, you can dynamically add custom filters. In the istio configuration file, you can configure the backup database as a parameter in istio, so that the IP address of the backup database can be controlled. configuration.

Further, please refer to FIG. 2. FIG. 2 is an implementation flow chart of a database multi-write and disaster recovery method provided by this application, including:

1. The client establishes a connection to database cluster A and performs write or read operations. Database cluster A and database cluster B have enabled the Envoy proxy for service management;

2. When the Client establishes a connection to the database cluster A to perform operations, the tcp traffic is hijacked by the Envoy proxy and passed to the filter in the Envoy proxy for processing;

3. The traffic is passed to the custom Wasm filter for processing database traffic for processing. The processing flow is as follows:

(1) According to the bytes parsed from the traffic request, it is judged whether it conforms to the database communication protocol, if so, proceed to the next step, and if not, directly skip the subsequent processing;

(2) Establish a connection with the backup database cluster B according to the address information of the backup database cluster B;

(3) If the command of the write type is obtained, it is forwarded to the database cluster B at the same time to complete the multi-write operation of the database;

(4) If the command of the read type is obtained, the response information of the command is obtained to determine whether the read operation is executed successfully, and if it fails, the command is forwarded to the backup database cluster B to obtain the backup database cluster B. Backup data, so as to achieve the characteristics of database backup disaster recovery.

It can be seen that the database multi-write method provided by the embodiment of the present application deploys the Envoy proxy in each database cluster, and sets the relevant information of the standby database cluster corresponding to its own database cluster in the Envoy proxy, so as to establish a backup database cluster based on this information. On this basis, the Envoy agent intercepts the data writing instructions received by its own database cluster, and after obtaining the data to be written, writes it to the standby database cluster, thereby realizing database reading and writing. Obviously, this implementation method can realize automatic database multi-writing without code modification, effectively improves the efficiency of database multi-writing, and reduces research and development costs at the same time.

In order to solve the above-mentioned technical problems, the present application also provides a database multi-writing device, please refer to FIG. 3, which is a schematic structural diagram of a database multi-writing device provided by the present application. The database multi-writing device may include:

The instruction interception module 1 is used for when the first database cluster receives the write instruction, the Envoy proxy deployed in the first database cluster intercepts the write instruction;

A data determination module 2, configured to determine the data to be written according to the write instruction;

The data rewriting module 3 is configured to establish a connection with the second database cluster according to the pre-stored information of the second database cluster, and write the data to be written into the second database cluster.

It can be seen that the database multi-writing device provided by the embodiment of the present application deploys the Envoy agent in each database cluster, and sets the relevant information of the standby database cluster corresponding to its own database cluster in the Envoy agent, so as to establish a backup database cluster based on this information. On this basis, the Envoy agent intercepts the data writing instructions received by its own database cluster, and after obtaining the data to be written, writes it to the standby database cluster, thereby realizing database reading and writing. Obviously, this implementation method can realize automatic database multi-writing without code modification, effectively improves the efficiency of database multi-writing, and reduces research and development costs at the same time.

As an optional embodiment, the database multi-writing device may also include a protocol judging module, which is used to analyze the write command to obtain the traffic protocol before determining the data to be written according to the write command; to judge whether the traffic protocol is It complies with the database communication protocol; if the traffic protocol conforms to the database communication protocol, the step of determining the data to be written according to the write instruction is performed.

As an optional embodiment, the database multi-writing device may also include a data reading module, and the data reading module may include:

A response information acquisition unit, configured to acquire response information corresponding to the read instruction when the first database cluster receives the read instruction;

A read operation judging unit, configured to determine whether the read operation is successful according to the response information;

A read instruction forwarding unit, configured to forward the read instruction to the second database cluster if the read operation is unsuccessful;

A read data acquisition unit, configured to acquire the read data fed back by the second database cluster according to the read instruction;

The read data feedback unit is used to feed back the read data to the initiator of the read command.

As an optional embodiment, the above-mentioned data reading module may also include a protocol judging unit, which is used to analyze the reading instruction and obtain the traffic protocol before obtaining the response information corresponding to the reading instruction; judge whether the traffic protocol conforms to A database communication protocol; if the traffic protocol conforms to the database communication protocol, then execute the step of obtaining the response information corresponding to the read command.

As an optional embodiment, the data reading module may further include an alarm prompt module, configured to output an alarm prompt when the read data fed back by the second data cluster is not obtained.

As an optional embodiment, the aforementioned Envoy agents are deployed in each database cluster, and the Envoy agents in each database cluster are created through service grid technology and Wasm technology.

As an optional embodiment, the above data multi-writing module 3 may be specifically configured to establish a connection with the second database cluster according to the pre-stored address information of the second database cluster.

For the introduction of the device provided in this application, please refer to the above method embodiment, and this application will not repeat it here.

In order to solve the above technical problems, this application also provides a database multi-writing system, please refer to Figure 4, Figure 4 is a schematic structural diagram of a database multi-writing system provided by this application, the database multi-writing system may include:

memory 10 for storing computer programs;

The processor 20 is configured to implement the steps of any one of the database multi-writing methods described above when executing the computer program.

For the introduction of the system provided by this application, please refer to the above method embodiment, and this application will not repeat it here.

In order to solve the above problems, this application also provides a computer-readable storage medium, please refer to FIG. 5 , which is a schematic structural diagram of a computer-readable storage medium provided by this application. A computer program 602 is stored, and when the computer program 602 is executed by the processor, the steps of any one of the database multi-writing methods described above can be realized.

The computer-readable storage medium 601 may include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc., which can store various programs. The medium of the code.

For the introduction of the computer-readable storage medium provided by the present application, please refer to the foregoing method embodiments, and the present application does not repeat it here.

Each embodiment in the description is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and for the related information, please refer to the description of the method part.

Professionals can further realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software or a combination of the two. In order to clearly illustrate the possible For interchangeability, in the above description, the composition and steps of each example have been generally described according to their functions. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be directly implemented by hardware, software modules executed by a processor, or a combination of both. The software module can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM or known in the technical field in any other form of storage medium.

The technical solution provided by the present application has been introduced in detail above. In this paper, specific examples are used to illustrate the principles and implementation methods of the present application, and the descriptions of the above embodiments are only used to help understand the methods and core ideas of the present application. It should be pointed out that those skilled in the art can make some improvements and modifications to the application without departing from the principle of the application, and these improvements and modifications also fall within the protection scope of the application.

Claims

A database multi-writing method is characterized in that, comprising:

When the first database cluster receives the write command, the Envoy proxy deployed in the first database cluster intercepts the write command;

determining data to be written according to the write instruction;

Establishing a connection with the second database cluster according to the pre-stored second database cluster information, and writing the data to be written into the second database cluster.
The database multi-writing method according to claim 1, wherein before determining the data to be written according to the writing instruction, further comprising:

Analyzing the write command to obtain a traffic protocol;

Judging whether the traffic protocol conforms to the database communication protocol;

If the traffic protocol conforms to the database communication protocol, the step of determining the data to be written according to the write instruction is executed.
The database multi-writing method according to claim 1, further comprising:

When the first database cluster receives a read instruction, obtain response information corresponding to the read instruction;

determining whether the read operation is successful according to the response information;

If the read operation is unsuccessful, forward the read instruction to the second database cluster;

Acquiring the read data fed back by the second database cluster according to the read instruction;

Feedback the read data to the initiator of the read command.
The database multi-writing method according to claim 3, wherein, before obtaining the response information corresponding to the read instruction, further comprising:

Analyzing the read command to obtain a traffic protocol;

Judging whether the traffic protocol conforms to the database communication protocol;

If the traffic protocol conforms to the database communication protocol, the step of acquiring the response information corresponding to the read command is executed.
The database multi-writing method according to claim 3, further comprising:

When the read data fed back by the second data cluster is not obtained, an alarm prompt is output.
The database multi-writing method according to claim 1, wherein the Envoy agent is deployed in each database cluster, and the Envoy agent in each database cluster is created by service grid technology and Wasm technology.
The database multi-writing method according to claim 1, wherein said establishing a connection with the second database cluster according to the pre-stored information of the second database cluster comprises:

Establishing a connection with the second database cluster according to the pre-stored address information of the second database cluster.
A database multi-writing device is characterized in that it comprises:

An instruction interception module, configured to intercept the write instruction by an Envoy agent deployed in the first database cluster when the first database cluster receives the write instruction;

A data determination module, configured to determine the data to be written according to the write instruction;

The data multi-writing module is configured to establish a connection with the second database cluster according to the pre-stored second database cluster information, and write the data to be written into the second database cluster.
A database multi-write system is characterized in that it comprises:

memory for storing computer programs;

A processor, configured to implement the steps of the database multi-writing method according to any one of claims 1 to 7 when executing the computer program.
A computer-readable storage medium, characterized in that, a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the multi-write database according to any one of claims 1 to 7 is realized method steps.