WO2025001842A1 - Distributed database, message processing method and apparatus, and electronic device - Google Patents

Abstract

The present application relates to a distributed database, a message processing method and apparatus, and an electronic device. The distributed database comprises: a database management node, a main service component control unit and a plurality of service components, wherein the database management node is in communication connection with the main service component control unit, and is configured to send a first message to the main service component control unit, or receive a second message from the main service component control unit; the main service component control unit is in communication connection with the plurality of service components, and is configured to forward the first message to each service component, or forward to the database management node a second message from each service component; and each service component is configured to receive the first message from the main service component control unit, or send the second message to the main service component control unit.

Description

Distributed database, message processing method, device and electronic device

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to patent application No. 202310793030.1 filed with the China Patent Office on June 29, 2023, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to but is not limited to the field of databases.

Background Art

The database supports multi-tenancy, and the data access and data storage of different tenants are isolated to ensure data security. Each tenant needs to have a corresponding tenant configuration, and the configuration information of the tenant configuration is used to specify the tenant ID, tenant name, primary and backup bureaus, and other information of the tenant. The power-on and message interaction of each module of the database depends on the correctness of the configuration information.

Distributed databases need to back up data, so there are multiple copies of data. Each tenant has a corresponding primary or backup office (for example, the primary and backup offices can be set up in different locations). The current networking mode is generally: the database has two offices, the primary office and the backup office, and each office has two tenants who back up data to each other. The business accesses the database through the client.

When the client executes the power-on process, it needs to obtain the configuration message from the database management node of the active station, and then obtain the distribution information and status information of the corresponding tenant's data node based on the tenant ID, tenant name, active and standby station information contained in the obtained configuration message, and finally reach the power-on success state.

Assuming there are 1,000 clients, when a single node of the database data switches state, the management node needs to send 1,000 notification messages to the client to notify it. If the state of the shards within 50 nodes switches, the management node needs to send 1,000*50 messages to the client in a short period of time.

It can be seen that there are always a lot of interactive messages between the database management node and other modules. When the database scale reaches a certain level, the CPU usage of the database management node due to message interaction will increase. Consumption will become a bottleneck, which greatly limits the capacity and processing performance of the database.

Summary of the invention

The present application provides a distributed database, a message processing method, a device and an electronic device.

In a first aspect, the present application provides a distributed database, comprising: a database management node, a main service component control unit and multiple service components; the database management node is communicatively connected to the main service component control unit, and is configured to send a first message to the main service component control unit, or to receive a second message from the main service component control unit; the main service component control unit is communicatively connected to the multiple service components, and is configured to forward the first message to each of the service components, or to forward the second message from each of the service components to the database management node; the service component is configured to receive the first message from the main service component control unit, or to send the second message to the main service component control unit.

In a second aspect, the present application provides a message processing method, applied to a main service component control unit, comprising: receiving a first message from a database management node; forwarding the first message to each of the service components; or, receiving a second message from each of the service components; forwarding the second message from each of the service components to the database management node.

In the third aspect, the present application provides a message processing method, applied to a service component, comprising: receiving the first message from the main service component control unit, the first message being received by the main service component control unit from a database management node; or, sending the second message to the main service component control unit so that the main service component control unit forwards the second message to the database management node.

In a fourth aspect, the present application provides a message processing device, applied to a main service component control unit, comprising: a first receiving module, configured to receive a first message from a database management node; a first forwarding module, configured to forward the first message to each of the service components; or, a second receiving module, configured to receive a second message from each of the service components; a second forwarding module, configured to forward the second message from each of the service components to the database management node.

In the fifth aspect, the present application provides a message processing device, applied to a service component, including: a third receiving module, configured to receive the first message from the main service component control unit, the first message is received by the main service component control unit from a database management node; or, a first sending module, configured to send the second message to the main service component control unit, so that the main service component control unit forwards the second message to the database management node.

In a sixth aspect, the present application provides an electronic device comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; the memory is configured to store a computer program; and the processor is configured to implement the message processing method described in any one of the second aspect or the message processing method described in any one of the third aspect when executing the program stored in the memory.

In the seventh aspect, the present application provides a computer-readable storage medium, on which a program of a message processing method is stored. When the program of the message processing method is executed by a processor, the message processing method described in any one of the second aspect, or the message processing method described in any one of the third aspect, is implemented.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

FIG1 is a physical networking architecture of a distributed database provided in an embodiment of the present application;

FIG2 is a logical architecture of a service component provided in an embodiment of the present application;

FIG3 is a flow chart of a message processing method provided in an embodiment of the present application;

FIG4 is a flowchart of another message processing method provided in an embodiment of the present application;

FIG5 is a schematic diagram of a combination of multiple service components provided in an embodiment of the present application;

FIG6 is a structural diagram of an electronic device provided in an embodiment of the present application.

DETAILED DESCRIPTION

In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

When the database scale reaches a certain level, the CPU consumption of the database management node due to message interaction will become a bottleneck, which greatly limits the capacity and processing performance of the database. To this end, the embodiments of the present application provide a distributed database, message processing method, device and electronic device under the architecture of large-capacity networking, which can at least solve the problem of a surge in the number of message interactions and performance bottlenecks caused by distribution changes caused by state changes or expansion and contraction of database management nodes.

An embodiment of the present application provides a distributed database, which includes: a main station and a backup station, etc. In actual networking, there may be a network of multiple stations. Taking only the main station and the backup station as an example, the networking architecture of the main station and the backup station is the same, wherein the main station or the backup station can be shown in Figure 1, including: a database management node 11, a main service component control unit 12 and multiple service components 13, and the service component 13 includes a client.

The database management node 11 is in communication connection with the main service component control unit 12 , and is used to send a first message to the main service component control unit 12 , or receive a second message from the main service component control unit 12 .

The main service component control unit 12 is in communication connection with a plurality of service components 13 , and is used to forward the first message to each of the service components 13 , or to forward the second message from each of the service components 13 to the database management node 11 .

The service component 13 is used to receive the first message from the main service component control unit 12, or send the second message to the main service component control unit 12.

In the embodiment of the present application, the service component is managed by the main service component control unit. The first message of the database management node is not sent directly to the service component, but is sent to the main service component control unit, and then forwarded to the service component by the main service component control unit; similarly, the service component The second message of the component is not sent directly to the database management node, but is sent to the main service component control unit, and then forwarded to the database management node by the main service component control unit, so that messages from different offices can be isolated.

The embodiment of the present application realizes physical layering of the networking framework of the distributed database by using the main service component control unit, realizes message diversion through the main service component control unit, reduces the processing pressure of the database management node caused by message interaction, effectively solves the performance bottleneck problem of the database management node, improves the processing performance of the distributed database, and, since the occurrence of performance bottlenecks is avoided, it can be more convenient to expand the distributed capacity and increase the capacity of the distributed database.

In one implementation of the present application, in order to facilitate data backup, each bureau has a main service component control unit 12 and a backup service component control unit 14, that is, based on the aforementioned embodiment, the distributed database also includes: a backup service component control unit 14.

The backup service component control unit 14 is communicatively connected to multiple service components 13, and is used to forward the first message to each service component 13 when the main service component control unit 12 is not working, or forward the second message from each service component 13 to the database management node 11.

In order to make the data in the backup service component control unit 14 consistent with the data in the main service component control unit 12, when the main service component control unit 12 is working, the main service component control unit 12 can automatically synchronize the received first message or second message to the backup service component control unit 14.

Based on the scheme of the aforementioned embodiment, since the performance load of the main service component control unit 12 may increase as an "intermediate role", the service components 13 need to be grouped immediately. Therefore, in one embodiment of the present application, multiple service components 13 are divided into at least one service component combination. Exemplarily, every 20 (adjustable) service components 13 are grouped together, and a group leader, i.e., the main service component, is logically elected, and the remaining service components 13 are slave service components. That is to say, each service component combination includes: a main service component and several slave service components, and the main service component is responsible for interacting with the main service component control unit 12 and forwarding messages to the remaining slave service components in the group.

The master service component is used to forward the first message to each of the slave service components, or to forward the second message from each of the slave service components to the master service component Control unit 12.

The slave service component is used to receive the first message from the master service component, or to send the second message to the master service component.

In order to further logically layer the networking framework of the distributed database, a multi-process mode can be adopted in the service component 13. In the multi-process mode, the main process is responsible for external message interaction, and other auxiliary processes interact with the main process message. Therefore, as shown in Figure 2, in one embodiment of the present application, each of the service components 13 includes: a main process and multiple auxiliary processes.

The main process is used to forward the first message to each of the auxiliary processes, or to forward the second message from each of the auxiliary processes to the main service component control unit 12.

The auxiliary process is used to receive the first message from the main process, or to send the second message to the main process.

In order to further logically layer the networking framework of the distributed database, a multi-threaded mode can be adopted in the service component 13. In the multi-threaded mode, the main thread is responsible for external message interaction, and the status information of the auxiliary thread is provided by the main thread. Therefore, as shown in Figure 2, in one embodiment of the present application, the main process includes: an external interaction thread, a first main thread, and multiple first auxiliary threads.

The external interaction thread is used to forward the first message to the first main thread and each auxiliary process, or to forward the second message from the first main thread or each auxiliary process to the main service component control unit 12.

The first main thread is used to forward the first message to each of the first auxiliary threads, or to forward the second message from each of the first auxiliary threads to the external interaction thread.

The first auxiliary thread is used to receive the first message from the first main thread, or to send the second message to the first main thread.

As shown in FIG. 2 , the auxiliary process may include only one main thread. In one implementation of the present application, the auxiliary process includes: a second main thread.

The second main thread is used to receive the first message from the external interaction thread, or send the second message to the external interaction thread.

As shown in FIG. 2 , the auxiliary process includes not only a main thread but also an auxiliary thread. In one embodiment of the present application, the auxiliary process also includes: a second auxiliary thread.

The second main thread is further used to forward the first message from the external interaction thread to the second auxiliary thread, or send the second message to the external interaction thread.

The second auxiliary thread is used to receive the first message from the second main thread, or send the second message to the second main thread.

After the above physical and logical layering, the message interaction pressure of each role in the distributed database networking framework is not high, which effectively solves the performance bottleneck problem of the database management node.

In another embodiment of the present application, as shown in Figures 3 and 4, a message processing method is also provided, which is applied to the main service component control unit, including: step S101, receiving a first message from a database management node; step S102, forwarding the first message to each of the service components; or, step S202, receiving a second message from each of the service components; step S203, forwarding the second message from each of the service components to the database management node.

Each time the main service component control unit sends the first message, it carries the grouping information (starting component identifier and terminating component identifier), and the service component does not need to store the grouping information. The first message sent by the main service component control unit to all service components is the same, which can avoid repeated encoding and compression of messages. This requires that all grouping information must be carried in the first message. The first message carries the starting component identifier and terminating component identifier of each service component combination, but does not carry the component identifier of each service component. Therefore, the memory occupied by the grouping information needs to be as small as possible.

The embodiment of the present application uses the main service component control unit as an intermediate role to realize the diversion of the first message or the second message, reduce the processing pressure of the database management node due to message interaction, effectively solve the performance bottleneck problem of the database management node, and improve the processing performance of the distributed database. In addition, since the occurrence of performance bottlenecks is avoided, it can be more convenient to expand the distributed capacity and increase the capacity of the distributed database.

In another embodiment of the present application, the method also includes: obtaining a first number of the service components registered on itself; when the first number exceeds a minimum group number threshold, determining the number of groups based on the first number, the minimum group number threshold and the maximum group number threshold.

Further, the number of packets = min (maximum number of packets threshold, max (minimum number of packets threshold, sqrt (first number))).

The first number of service components are grouped according to the grouping quantity to obtain a plurality of service component combinations.

As an example, when the number of service components registered on the main service component control unit exceeds 20, grouping is required, and the number of groupings is min(33, max(20, sqrt(SC number))), that is, at least 20 groups and at most 33 groups, so that the number of service components in each group is basically balanced.

Furthermore, the first number of service components are grouped according to the grouping quantity to obtain multiple service component combinations, including: obtaining a component identifier of each of the service components; sorting the first number of service components according to the component identifier; and grouping the identifier sequences obtained by sorting to obtain multiple service component combinations.

That is, all registered service components are sorted and grouped according to the globally unique identifier, that is, the component identifier.

In another embodiment of the present application, the method further includes: for each service component combination, obtaining the status parameters of each service component in the service component combination; and determining the main service component and the slave service component in the service component combination based on the status parameters of each service component.

Because when the main service component selected by the main service component control unit is unreachable, all the slave service components of this group cannot receive the first message. In order to reduce this risk, the main service component control unit can only select a service component in normal status in the service component list as the group leader, that is, the main service component.

In another embodiment of the present application, the method further includes: in the case where any of the service component combinations has a service component to be added or deleted, obtaining the time interval between the current moment and the moment when the second message was last received from the service component combination or the first message was last forwarded to the service component combination; When the preset time interval has passed, it is allowed to add the service component to be added to the service component combination, or to delete the service component to be deleted from the service component combination.

When the service component combination changes, the two second messages will be sent through different paths, which may cause message disorder. To avoid this situation, the change of the service component combination is restricted: if the time interval from the last message has exceeded the preset time interval (such as 5 seconds), the preset time interval is a safety interval and it can be regarded as no notification message in transit. Then the service components can be added and exited without restriction and regrouped.

In another embodiment of the present application, the method also includes: when the time interval does not exceed the preset time interval, determining whether the service component to be deleted is the main service component; the service component to be deleted refers to a service component that needs to exit the service component combination when it is deregistered due to timeout or the service component status is abnormal.

When the service component to be deleted is the main service component, adjust the starting component identifier of the service component combination, and determine the service component corresponding to the starting component identifier as the new main service component; when the service component to be deleted is not the main service component, directly delete the service component.

If the exiting service component is not the group leader, for example, service component 4 or service component 5 in Figure 5 (the gray box in Figure 5 is the service component that actually exists in the corresponding service component combination) exits group 1, there is no need to adjust the grouping immediately. The grouping can be adjusted to balance the group size when the time interval condition is met later. If the exiting service component is the group leader, for example, service component 1 in Figure 5 exits group 1, the starting component identifier of group 1 can be adjusted (service component 4 becomes the new group leader), and no adjustments are made to other groups. The grouping can be adjusted to balance the group size when the time interval condition is met later.

In another embodiment of the present application, the method further includes: when the time interval does not exceed the preset time interval, determining whether the service component to be added is located between the starting component identifier and the terminating component identifier of the service component combination; when the service component to be added is located between the starting component identifier and the terminating component identifier of the service component combination, directly adding the service component to be added to the service component combination; when the service component to be added is not located between the starting component identifier and the terminating component identifier of the service component combination, adjusting the starting component identifier or the terminating component identifier based on the component identifier of the service component to be added, and adding the service component to be added to the service component combination. Service components.

If the newly added service component is already within the scope of a certain service component combination, such as service component 2 or service component 3 in Figure 5 joining group 1, there is no need to adjust the grouping immediately. The grouping can be adjusted to balance the group size when the time interval condition is met later. If the newly added service component is not within the scope of a certain group, such as service component 6 or service component 7 in the figure below joining group 1, the termination component identifier of group 1 can be adjusted (group 1 is expanded but the group leader of group 1 remains unchanged), and other groups are not adjusted. The grouping can be adjusted to balance the group size when the time interval condition is met later.

In another embodiment of the present application, as shown in Figures 3 and 4, a message processing method is also provided, which is applied to the service component, including: step S103, receiving the first message from the main service component control unit, the first message is received by the main service component control unit from the database management node; or, step S201, sending the second message to the main service component control unit, so that the main service component control unit forwards the second message to the database management node.

The embodiment of the present application realizes the main service component control unit as an intermediate role through message interaction between the service component and the main service component control unit, thereby diverting the first message or the second message, reducing the processing pressure of the database management node due to the message interaction, and effectively solving the performance bottleneck problem of the database management node, improving the processing performance of the distributed database, and because the occurrence of performance bottlenecks is avoided, it can be more convenient to expand the distributed capacity and increase the capacity of the distributed database.

In another embodiment of the present application, the method also includes: when the first message is received, extracting grouping information about at least one service component combination in the first message, the grouping information including: a starting component identifier and an ending component identifier; comparing its own component identifier with each of the starting component identifiers; when its own component identifier is the same as any of the starting component identifiers, determining itself as the main service component of the service component combination to which the starting component identifier belongs; and forwarding the first message to the slave service components corresponding to each component identifier between the starting component identifier and the ending component identifier.

When a service component receives a notification message, if its component ID matches the start component ID of a service component combination, then as the group leader, the main service component needs to forward the message to all members in the group, that is, the slave service components. All instantiated service components within the component identifier, default start component identifier and end component identifier range of the service component have been registered with the main service component control unit.

The main service component as the group leader does not forward messages depending on its own power-on status, tenants, and validity status of configuration information. If a group has only one service component, the grouping information of the group does not need to be included in the first message.

In another embodiment of the present application, a message processing device is also provided, which is applied to the main service component control unit, including: a first receiving module, used to receive a first message from a database management node; a first forwarding module, used to forward the first message to each of the service components; or, a second receiving module, used to receive a second message from each of the service components; a second forwarding module, used to forward the second message from each of the service components to the database management node.

In another embodiment of the present application, a message processing device is also provided, which is applied to the service component, including: a third receiving module, used to receive the first message from the main service component control unit, the first message is received by the main service component control unit from the database management node; or, a first sending module, used to send the second message to the main service component control unit, so that the main service component control unit forwards the second message to the database management node.

In another embodiment of the present application, an electronic device is provided, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; the memory is used to store computer programs; and the processor is used to implement the message processing method described in any of the aforementioned method embodiments when executing the program stored in the memory.

In the electronic device provided in the embodiment of the present application, the processor realizes the diversion of the first message or the second message through the main service component control unit as an intermediate role by executing the program stored in the memory, thereby reducing the processing pressure of the database management node caused by message interaction, effectively solving the performance bottleneck problem of the database management node, and improving the processing performance of the distributed database. In addition, since the occurrence of performance bottlenecks is avoided, it is easier to expand the distributed capacity and increase the capacity of the distributed database.

The communication bus 1140 mentioned in the above electronic device can be a peripheral component interconnect standard (PCI) bus or an extended industrial standard bus. The communication bus 1140 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, FIG6 only uses one thick line, but does not mean that there is only one bus or one type of bus.

The communication interface 1120 is used for communication between the above electronic device and other devices.

The memory 1130 may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

The above-mentioned processor 1110 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

In another embodiment of the present application, a computer-readable storage medium is further provided, on which a program of a message processing method is stored. When the program of the message processing method is executed by a processor, the steps of the message processing method described in any of the aforementioned method embodiments are implemented.

It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

The above description is only an exemplary embodiment of the present application, which enables those skilled in the art to understand or implement the present application. Various modifications to these embodiments will be of great benefit to those skilled in the art. It will be apparent that the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features of the present application.

Claims (20)

A distributed database comprises: a database management node, a main service component control unit and a plurality of service components; The database management node is in communication connection with the main service component control unit and is configured to send a first message to the main service component control unit, or receive a second message from the main service component control unit; The main service component control unit is in communication connection with a plurality of service components and is configured to forward the first message to each of the service components, or to forward the second message from each of the service components to the database management node; The service component is configured to receive the first message from the main service component control unit, or to send the second message to the main service component control unit. The distributed database according to claim 1, further comprising: a backup service component control unit; The backup service component control unit is communicatively connected to multiple service components, and is configured to forward the first message to each service component when the main service component control unit is not working, or to forward the second message from each service component to the database management node. The distributed database according to claim 1, wherein the plurality of service components are divided into at least one service component combination, each service component combination comprising: a master service component and a plurality of slave service components; The master service component is configured to forward the first message to each of the slave service components, or to forward the second message from each of the slave service components to the master service component control unit; The slave service component is configured to receive the first message from the master service component, or to send the second message to the master service component. The distributed database according to claim 1, wherein each of the service components comprises: a main process and a plurality of auxiliary processes; The main process is configured to forward the first message to each of the auxiliary processes, or forward the second message from each of the auxiliary processes to the main service component control unit; The auxiliary process is configured to receive the first message from the main process, or to send the second message to the main process. The distributed database according to claim 4, wherein the main process includes: an external interaction thread, a first main thread and a plurality of first auxiliary threads; The external interaction thread is configured to forward the first message to the first main thread and each of the auxiliary processes, or to forward the second message from the first main thread or each of the auxiliary processes to the main service component control unit; The first main thread is configured to forward the first message to each of the first auxiliary threads, or to forward the second message from each of the first auxiliary threads to the external interaction thread; The first auxiliary thread is configured to receive the first message from the first main thread, or to send the second message to the first main thread. The distributed database according to claim 5, wherein the auxiliary process includes: a second main thread; The second main thread is configured to receive the first message from the external interaction thread, or to send the second message to the external interaction thread. The distributed database according to claim 6, wherein the auxiliary process further comprises: a second auxiliary thread; The second main thread is further configured to forward the first message from the external interaction thread to the second auxiliary thread, or send the second message to the external interaction thread; The second auxiliary thread is configured to receive the first message from the second main thread, or to send the second message to the second main thread. A message processing method, applied to a main service component control unit, comprising: Receiving a first message from a database management node; Forwarding the first message to each of the service components; or, receiving a second message from each of the service components; Forward the second message from each of the service components to the database management node point. The message processing method according to claim 8, further comprising: Obtaining a first quantity of the service components registered on itself; In the case where the first number exceeds a minimum group number threshold, determining the number of groups according to the first number, the minimum group number threshold and the maximum group number threshold; The first number of service components are grouped according to the grouping quantity to obtain a plurality of service component combinations. The message processing method according to claim 9, wherein the first number of service components are grouped according to the number of groups to obtain a plurality of service component combinations, comprising: Obtaining a component identifier of each of the service components; sorting the first number of the service components according to the component identifiers; The sorted identification sequences are grouped to obtain multiple service component combinations. The message processing method according to claim 9, further comprising: For each service component combination, obtaining a state parameter of each service component in the service component combination; A master service component and a slave service component in the service component combination are determined based on the state parameter of each of the service components. The message processing method according to claim 9, further comprising: In the case that any of the service component combinations has a service component to be added or deleted, obtaining the time interval between the current moment and the moment when the second message was last received from the service component combination or the first message was last forwarded to the service component combination; In the case that the time interval exceeds the preset time interval, it is allowed to add the service component to be added to the service component combination, or to delete the service component to be deleted from the service component combination. The message processing method according to claim 12, further comprising: If the time interval does not exceed the preset time interval, determining whether the service component to be deleted is a main service component; If the service component to be deleted is a main service component, adjust the service group The starting component identifier of the component combination, and determining the service component corresponding to the starting component identifier as a new main service component; When the service component to be deleted is not the main service component, the service component is directly deleted. The message processing method according to claim 12, further comprising: In the case that the time interval does not exceed the preset time interval, determining whether the service component to be added is located between the start component identifier and the end component identifier of the service component combination; In the case where the service component to be added is located between the start component identifier and the end component identifier of the service component combination, directly adding the service component to be added to the service component combination; When the service component to be added is not located between the starting component identifier and the ending component identifier of the service component combination, the starting component identifier or the ending component identifier is adjusted based on the component identifier of the service component to be added, and the service component to be added is added to the service component combination. A message processing method, applied to a service component, comprising: Receiving a first message from a primary service component control unit, where the first message is received by the primary service component control unit from a database management node; or, A second message is sent to the main service component control unit so that the main service component control unit forwards the second message to the database management node. The message processing method according to claim 15, further comprising: Upon receiving the first message, extracting grouping information about at least one service component combination from the first message, the grouping information including: a start component identifier and an end component identifier; Comparing the component identification of the self with the identification of each starting component; When its component identifier is the same as any of the starting component identifiers, it determines itself as the main service component of the service component combination to which the starting component identifier belongs; The first message is forwarded to slave service components corresponding to each component identifier between the start component identifier and the end component identifier. A message processing device, applied to a main service component control unit, comprising: A first receiving module, configured to receive a first message from a database management node; A first forwarding module, configured to forward the first message to each of the service components; or, A second receiving module, configured to receive a second message from each of the service components; The second forwarding module is configured to forward the second message from each of the service components to the database management node. A message processing device, applied to a service component, comprising: A third receiving module is configured to receive a first message from the main service component control unit, where the first message is received by the main service component control unit from the database management node; or, The first sending module is configured to send a second message to the main service component control unit, so that the main service component control unit forwards the second message to the database management node. An electronic device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; a memory configured to store a computer program; The processor is configured to implement the message processing method described in any one of claims 8 to 14, or the message processing method described in any one of claims 15 to 16 when executing the program stored in the memory. A computer-readable storage medium having a program stored thereon, wherein when the program is executed by a processor, the message processing method described in any one of claims 8 to 14 or the message processing method described in any one of claims 15 to 16 is implemented.