Message processing system, method and equipment and storage medium

Abstract

The invention relates to a message processing system, method and device and a storage medium, and the system comprises a distribution configuration module which is used for receiving a message sent by a first service party, determining message middleware corresponding to an event type according to the event type of the message sent by the first service party, and sending the message middleware to the first service party; the message sent by the first service party is sent to the corresponding message middleware; the receiving configuration module is used for responding to a receiving request sent by a second service party and determining a target message needing to be received by the receiving request; and determining target message middleware where the target message is located, obtaining the target message from the target message middleware, and sending the target message to the second service party. According to the invention, the configuration resource and management cost of the service party can be reduced, and message processing can be completed more efficiently and conveniently.

Description

Technical Field

[0001] The present application relates to the technical field of message processing, and in particular, to a message processing system, method, device, and storage medium. Background Art

[0002] Currently, in the field of message processing, the general steps are: message reception, message processing, and message distribution. The system service needs to first receive messages from other services, and after processing based on business rules, repackage the information and then perform subsequent message distribution.

[0003] In the existing business message processing system, the distribution of relevant messages requires processing by the business logic service. Therefore, in the prior art, the business party of message processing needs to manage processes such as message reception, message processing, and message distribution in the service.

[0004] This process is relatively mechanical and complex, resulting in high requirements for service resources or development architecture design, and the configuration is relatively scattered with high management costs. Therefore, how to complete message processing more efficiently and conveniently is a technical problem that needs to be solved urgently. Summary of the Invention

[0005] Based on this, the present application provides a message processing system, method, device, and storage medium to solve the problems existing in the prior art.

[0006] In a first aspect, a message processing system is provided. The system includes:

[0007] A distribution configuration module: configured to receive a message sent by a first service party, determine a message middleware corresponding to the event type of the message sent by the first service party, and send the message sent by the first service party to the corresponding message middleware;

[0008] A reception configuration module: configured to, in response to a reception request sent by a second service party, determine a target message that the reception request needs to receive; determine a target message middleware where the target message is located, obtain the target message from the target message middleware, and send the target message to the second service party.

[0009] According to an implementable manner in an embodiment of the present application, the system further includes a processing configuration module, and the processing configuration module is configured to:

[0010] In response to the reception request sent by the second service party, determine a target message that the reception request needs to receive;

[0011] Determine a processing method corresponding to the target message based on pre-set processing configuration information;

[0012] Send the processing method to the second service provider.

[0013] According to an implementable manner in the embodiments of the present application, the distribution configuration module is further configured to:

[0014] Receive the new message obtained after the second service provider processes the target message based on the processing method;

[0015] Determine a new message middleware corresponding to the event type of the new message according to the event type of the new message, and send the new message to the new message middleware.

[0016] According to an implementable manner in the embodiments of the present application, the distribution configuration module is further configured to:

[0017] Determine different event messages according to the event type of the message sent by the first service provider, where the event messages are at least one;

[0018] Respectively determine the message middleware corresponding to each event message;

[0019] Send each of the event messages to the corresponding message middleware.

[0020] In a second aspect, a message processing method is provided, and the method includes:

[0021] Receive the message sent by the first service provider, determine the message middleware corresponding to the event type according to the event type of the message sent by the first service provider, and send the message sent by the first service provider to the corresponding message middleware;

[0022] In response to the reception request sent by the second service provider, determine the target message that the reception request needs to receive;

[0023] Determine the target message middleware where the target message is located, obtain the target message from the target message middleware, and send the target message to the second service provider.

[0024] According to an implementable manner in the embodiments of the present application, the method further includes:

[0025] In response to the reception request sent by the second service provider, determine the target message that the reception request needs to receive;

[0026] Determine the processing method corresponding to the target message based on the pre-set processing configuration information;

[0027] Send the processing method to the second service provider.

[0028] According to an implementable manner in an embodiment of the present application, the method further includes:

[0029] Receiving a new message obtained by the second service party after processing the target message based on the processing method;

[0030] According to the event type of the new message, determining a new message middleware corresponding to the event type of the new message, and sending the new message to the new message middleware.

[0031] According to an implementable manner in an embodiment of the present application, the receiving the message sent by the first service party, determining, according to the event type of the message sent by the first service party, a message middleware corresponding to the event type, and sending the message sent by the first service party to the corresponding message middleware includes:

[0032] Determining different event messages according to the event type of the message sent by the first service party, where the event messages are at least one;

[0033] Respectively determining a message middleware corresponding to each event message;

[0034] Sending each event message to the corresponding message middleware.

[0035] In a third aspect, a computer device is provided, including:

[0036] At least one processor; and

[0037] A memory communicatively connected to the at least one processor; wherein,

[0038] The memory stores computer instructions executable by the at least one processor, and the computer instructions are executed by the at least one processor so that the at least one processor can execute the system involved in the second aspect above.

[0039] In a fourth aspect, a computer-readable storage medium is provided, on which computer instructions are stored, and characterized in that the computer instructions are used to cause a computer to execute the system involved in the second aspect above.

[0040] According to the technical content provided by the embodiments of the present application, the present application receives a message sent by a first service party through a distribution configuration module, determines a message middleware corresponding to the event type according to the event type of the message sent by the first service party, and sends the message sent by the first service party to the corresponding message middleware; through a receiving configuration module 102, in response to a receiving request sent by a second service party, determines a target message that the receiving request needs to receive; determines the target message middleware where the target message is located, obtains the target message from the target message middleware, and sends the target message to the second service party. A message processing system provided by the present application can, in the form of components, enable service parties that need to receive and distribute messages to reference the components. There is no need for the service parties to determine what middleware the message needs to be distributed to or from what middleware to receive the message. All functions are managed by a unified service, and a general component is provided. After the user references the component, the general receiving and sending processes of component message processing can be directly implemented. The present application reduces the configuration resources and management costs of the service parties and can complete message processing more efficiently and conveniently. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 FIG. is a structural block diagram of a message processing system in an embodiment;

[0042] Figure 2 FIG. is a structural block diagram of a message processing system in another embodiment;

[0043] Figure 3 FIG. is a schematic diagram of message processing in the prior art;

[0044] Figure 4 FIG. is one of the schematic diagrams of a message processing system in an embodiment;

[0045] Figure 5 FIG. is another schematic diagram of a message processing system in an embodiment;

[0046] Figure 6 FIG. is a schematic flow diagram of a message processing method in an embodiment;

[0047] Figure 7 FIG. is a schematic structural diagram of a computer device in an embodiment. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0048] The following further details the present application in conjunction with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0049] Figure 1 FIG. is a structural diagram of a message processing system provided by an embodiment of the present application. First, refer to Figure 1Describe the present application in detail.

[0050] As Figure 1 shown, a message processing system 100 provided by the present application includes:

[0051] A distribution configuration module 101: configured to receive a message sent by a first service party, determine a message middleware corresponding to the event type according to the event type of the message sent by the first service party, and send the message sent by the first service party to the corresponding message middleware;

[0052] A receiving configuration module 102: configured to, in response to a receiving request sent by a second service party, determine a target message that the receiving request needs to receive; determine a target message middleware where the target message is located, obtain the target message from the target message middleware, and send the target message to the second service party.

[0053] Specifically, as Figure 1 shown, the present application provides a message processing system in the form of a component, which allows service parties that need to receive and distribute messages to reference the component and configure the central message service address, thus completing the reference of the component. After that, the receiving and distribution configurations can be performed in the configuration center. For message distribution configuration, configure the scanning and distribution target middleware addresses for different message events, and distribute through message events. For receiving configuration, configure the message receiving middleware address, and the component will automatically generate the message listening and receiving content based on the configured information.

[0054] Figure 3 FIG. is a schematic diagram of message processing in the prior art. In the prior art, when traditional services perform relevant message distribution, it is necessary to clearly specify in the service which middleware this message needs to be distributed to, and the middleware is different in different environments. When the processing service needs to receive a message, it also needs to specify which middleware to obtain the message of which event from, and if this message needs to be processed, a method call for the processing method needs to be made after receiving it. If multiple methods all require method calls for processing, it is necessary to continuously add service code in the method after receiving to implement. When a new message generated after the message is processed is also required to be specified and distributed to the corresponding middleware.

[0055] The present application provides a message processing system in the form of a component, which includes a distribution configuration module and a receiving configuration module. First, the distribution configuration module receives a message sent by a first service party. As Figure 4As shown, the first service provider is the message sending service provider A. This first service provider only needs to send a message to the message processing system component, and does not need to specify in the first service provider to which middleware the message needs to be distributed. The distribution configuration module receives the message a sent by the first service provider, and then determines the message middleware 1 corresponding to the event type A1 according to the event type of the message sent by the first service provider, and sends the message a sent by the first service provider to the corresponding message middleware 1. Secondly, as Figure 4 shown, the second service provider is the message processing service provider B. The second service provider only needs to send a receive request to the message processing system component, and does not need to specify in the second service provider from which middleware to obtain the message of what event. The receive configuration module 102 of the message processing system responds to the receive request sent by the second service provider, and determines the target message that the receive request needs to receive. Further, it determines the target message middleware where the target message is located, obtains the target message from the target message middleware, and sends the target message to the second service provider. For example, in response to the receive request sent by the second service provider, it is determined that the target message that the receive request needs to receive is the message a. Further, it is determined that the target message middleware where the target message a is located is the message middleware 1, obtains the target message a from the target message middleware, that is, the message middleware 1, and sends the target message a to the second service provider B.

[0056] In this application, the message sender needs to implement the method of message sending, and can send this event message by calling the implemented general sending method. When calling the component connected to the message processing system, the message processing system can perform corresponding configurations based on this, and configure the middleware address to which the message needs to be sent.

[0057] It can be seen that in the embodiment of the present application, the distribution configuration module receives the message sent by the first service party, determines the message middleware corresponding to the event type according to the event type of the message sent by the first service party, and sends the message sent by the first service party to the corresponding message middleware; the receiving configuration module 102 determines the target message that the receiving request needs to receive in response to the receiving request sent by the second service party; determines the target message middleware where the target message is located, obtains the target message from the target message middleware, and sends the target message to the second service party. A message processing system provided by the present application can be referenced by service parties that need to receive and distribute messages in the form of components, without the need for the service parties to determine which middleware the message needs to be distributed to or which middleware to receive the message from. All functions are managed by a unified service, and a general component is provided. After the user references the component, the general receiving and sending processes of component message processing can be directly implemented. The present application reduces the configuration resources and management costs of the service party and can complete message processing more efficiently and conveniently.

[0058] In an embodiment of the present application, the system further includes a processing configuration module 103, and the processing configuration 103 module is used to: determine the target message that the receiving request needs to receive in response to the receiving request sent by the second service party; determine the processing method corresponding to the target message based on the pre-set processing configuration information; and send the processing method to the second service party.

[0059] Specifically, as Figure 2 shown, a message processing system provided by the present application further includes a processing configuration module 103. As Figure 4 shown, and in combination with Figure 5 , when the second service party sends a receiving request, the processing configuration module determines the processing method corresponding to the target message based on the pre-set processing configuration information; and sends the processing method to the second service party. The processing configuration information is what kind of message needs to be processed by what kind of processing method pre-set. When the receiving party server needs to receive a message, only the receiving method needs to be implemented. After registering with the message center service, the message center will perform message receiving configuration based on the information support, configuring which message with which event name to receive from which middleware. When the receiving party needs to perform message processing, it needs to implement the component message processing method, and perform message processing and generate a new event in the actual implementation method. Based on this information, the message center can perform configuration, configuring which message event received needs to be processed by what kind of processing method.

[0060] For example, service provider A sends a message: The customer has put the goods in the shopping cart for more than half an hour. After receiving the message, the message processing system determines the processing method corresponding to the target message based on the pre-set processing configuration information. The processing method includes analyzing the customer's purchase tendency, specifically including checking the customer's payment status. If the customer has not paid, a message will be sent to the customer. If the payment has been completed, no message will be sent. The processing method is sent to the second service provider B. Service B receives the message and can perform the following processing: check the customer's payment status. If the customer has not paid, send a message and ask if there are any questions. If the payment has been completed, no message will be sent.

[0061] In an embodiment of the present application, the message processing system further includes a processing configuration module. Through the message processing system of the present application, service providers that need to receive, process, and distribute messages can perform component references and configure the central message service address, thus completing the component reference. After that, configurations for receiving, processing, and distributing can be performed in the configuration center: for the receiving configuration, the address of the message receiving middleware is received, and the component will automatically generate the message listening and receiving content based on the configured information; then, the message processing configuration is performed, and the corresponding service method of the registered service needs to be configured. This service method needs to inherit the general processing class of the technical component to complete the unified management of the outer layer structure of the message input content and the processing output content; after processing, the message distribution configuration is performed, and the addresses of the target middleware for scanning and distributing different message events are configured, and the distribution is performed through the message events.

[0062] In an embodiment of the present application, the distribution configuration module 101 is further configured to: determine different event messages according to the event type of the message sent by the first service provider, where the event messages are at least one; respectively determine the message middleware corresponding to each event message; and send each event message to the corresponding message middleware.

[0063] Specifically, as Figure 4 shown, according to the event type of the message A sent by the first service provider, different event messages are determined, where the event messages are at least one. For example, event message A1 and event message A2 are generated, and then the message middleware corresponding to each event message is respectively determined. For example, it is confirmed that event message A1 corresponds to message middleware 1, and event message A2 corresponds to message middleware 2. Each event message is sent to the corresponding message middleware. For example, event message A1 is sent to message middleware 1, and event message A2 is sent to message middleware 2.

[0064] In an embodiment of the present application, the distribution configuration module 101 is further configured to: receive the new message obtained by the second service party after processing the target message based on the processing method; determine a new message middleware corresponding to the event type of the new message according to the event type of the new message, and send the new message to the new message middleware.

[0065] Specifically, as Figure 4 shown, the second service party, that is, service party B, obtains a new message after processing the target message based on a pre-configured processing method. For example, service party B obtains a new message A3 after processing the target message A2.

[0066] After the message center service, that is, the message processing system, receives the new message A3, it determines a new message middleware corresponding to the event type of the new message A3 according to the event type of the new message A3. For example, it determines that the corresponding new message middleware is message middleware 3, and sends the new message A3 to the message middleware 3.

[0067] It can be seen that the embodiment of the present application solves the problems of unified configuration, process separation, and component simplification for message reception, processing, and distribution in distributed services. Unified configuration means that all services using only need to reference the component address, and at the same time, relevant message reception addresses, processing service names, message sending addresses, sending conditions, etc. can be uniformly configured and managed. Process separation mainly means that the use of configuration-based components automatically generates relevant call codes based on configuration information. If no configuration is performed, no corresponding processing will be carried out, which reduces the coupling of different processes. Moreover, the configuration of the process does not affect the modification of the main service, only configuration updates are required, reducing the coupling between logic and services. Component simplification means that all functions are managed by a unified service, and a general component is provided. After the user quotes the component, they can directly implement the general reception class, processing class, and sending class for component message processing to complete the registration of relevant required processes.

[0068] Figure 6 The flowchart of a message processing method provided by an embodiment of the present application, as Figure 6 shown, the method may include the following steps:

[0069] Step 601: Receive the message sent by the first service party, determine the message middleware corresponding to the event type according to the event type of the message sent by the first service party, and send the message sent by the first service party to the corresponding message middleware.

[0070] Step 602: In response to the reception request sent by the second service party, determine the target message that the reception request needs to receive.

[0071] Step 603: Determine the target message middleware where the target message is located, obtain the target message from the target message middleware, and send the target message to the second service party.

[0072] In an embodiment of the present application, the method further includes: in response to a reception request sent by the second service party, determining a target message that the reception request needs to receive; determining a processing method corresponding to the target message based on pre-set processing configuration information; and sending the processing method to the second service party.

[0073] In an embodiment of the present application, the method further includes: receiving a new message obtained after the second service party processes the target message based on the processing method; determining a new message middleware corresponding to the event type of the new message according to the event type of the new message, and sending the new message to the new message middleware.

[0074] In an embodiment of the present application, the receiving the message sent by the first service party, determining the message middleware corresponding to the event type according to the event type of the message sent by the first service party, and sending the message sent by the first service party to the corresponding message middleware includes: determining different event messages according to the event type of the message sent by the first service party, where the event messages are at least one; respectively determining the message middleware corresponding to each event message; and sending each event message to the corresponding message middleware.

[0075] In the embodiment of the present application, the distribution configuration module receives the message sent by the first service party, determines the message middleware corresponding to the event type according to the event type of the message sent by the first service party, and sends the message sent by the first service party to the corresponding message middleware; the reception configuration module 102 determines the target message that the reception request needs to receive in response to the reception request sent by the second service party; determines the target message middleware where the target message is located, obtains the target message from the target message middleware, and sends the target message to the second service party. A message processing system provided by the present application can be referenced by service parties that need to receive and distribute messages in the form of components. There is no need for the service party to determine what middleware the message needs to be distributed to or what middleware to receive the message from. All functions are managed by a unified service, and a general component is provided. After the user references the component, the general reception and sending processes of component message processing can be directly implemented. The present application reduces the configuration resources and management costs of the service party and can complete message processing more efficiently and conveniently.

[0076] It can be seen that the embodiments of the present application solve the problems of unified configuration, process separation, and component simplification for message reception, processing, and distribution in distributed services. Unified configuration means that all services that use the service only need to reference the component address. At the same time, relevant message reception addresses, processing service names, message sending addresses, sending conditions, etc. can all be uniformly configured and managed. Process separation mainly means that the use of configuration-based components automatically generates relevant call codes based on configuration information. If no configuration is performed, no corresponding processing will be carried out, which reduces the coupling of different processes. Moreover, the configuration of the process does not affect the modification of the main service, and only configuration updates are required, reducing the coupling between logic and services. Component simplification means that all functions are managed by a unified service, and common components are provided. After the user references the components, they can directly implement the common reception class, processing class, and sending class for component message processing to complete the registration of relevant required processes.

[0077] It should be understood that although Figure 6 the steps in the flowchart of Figure 1 are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in the present application, there is no strict order limit for the execution of these steps, and these steps can be executed in other orders. Moreover,

[0078] For the same and similar parts among the above embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for method embodiments, since they are basically similar to system embodiments, the description is relatively simple, and reference can be made to the relevant parts of the system embodiments for the relevant content.

[0079] It should be noted that the embodiments of the present application may involve the use of user data. In actual applications, within the scope permitted by applicable laws and regulations in the country of residence (such as when the user clearly consents, is effectively notified, and clearly authorizes the user, etc.), user-specific personal data can be used in the solutions described herein within the scope permitted by applicable laws and regulations.

[0080] According to an embodiment of the present application, the present application further provides a computer device and a computer-readable storage medium. The present application further provides a computer device, including at least one processor and a memory communicatively connected to the at least one processor; wherein, the memory stores computer instructions executable by the at least one processor, and the computer instructions are executed by the at least one processor so that the at least one processor can execute the message processing system described in any of the above embodiments.

[0081] As Figure 7 shown, it is a block diagram of a computer device according to an embodiment of the present application. The computer device is intended to represent various forms of digital computers or mobile devices. Among them, the digital computer may include a desktop computer, a portable computer, a workbench, a personal digital assistant, a server, a mainframe computer and other suitable computers. The mobile device may include a tablet computer, a smart phone, a wearable device, etc.

[0082] As Figure 7 shown, the computer device 700 includes a computing unit 701, a ROM 702, a RAM 703, a bus 704, and an input / output (I / O) interface 705. The computing unit 701, the ROM 702, and the RAM 703 are connected to each other through the bus 704. The input / output (I / O) interface 705 is also connected to the bus 704.

[0083] The computing unit 701 can execute various processes in the method embodiments of the present application according to the computer instructions stored in the read-only memory (ROM) 702 or the computer instructions loaded from the storage unit 708 into the random access memory (RAM) 703. The computing unit 701 can be various general and / or special processing components with processing and computing capabilities. The computing unit 701 may include, but is not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. In some embodiments, the method provided by the embodiments of the present application can be implemented as a computer software program, which is tangibly included in a computer-readable storage medium, such as the storage unit 708.

[0084] The RAM 703 can also store various programs and data required for the operation of the device 700. Part or all of the computer programs can be loaded and / or installed onto the device 700 via the ROM 702 and / or the communication unit 709.

[0085] The input unit 706, output unit 707, storage unit 708, and communication unit 709 in the computer device 700 can be connected to the I / O interface 705. Among them, the input unit 706 can be such as a keyboard, mouse, touch screen, microphone, etc.; the output unit 707 can be such as a display, speaker, indicator light, etc. The device 700 can exchange information, data, etc. with other devices through the communication unit 709.

[0086] It should be noted that the device may also include other components necessary for normal operation. It may also only include the components necessary to implement the solution of the present application, and does not necessarily include all the components shown in the figure.

[0087] The various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof.

[0088] The computer instructions for implementing the methods of the present application can be written in any combination of one or more programming languages. These computer instructions can be provided to the computing unit 701, such that when the computer instructions are executed by a computing unit 701 such as a processor, the steps involved in the method embodiments of the present application are executed.

[0089] The present application also provides a computer-readable storage medium, on which computer instructions are stored, and the computer instructions are used to cause a computer to execute the message processing method described in any of the above embodiments.

[0090] The computer-readable storage medium provided by the present application can be a tangible medium, which can contain or store computer instructions for executing the steps involved in the method embodiments of the present application. The computer-readable storage medium can include, but is not limited to, storage media in the forms of electronic, magnetic, optical, electromagnetic, etc.

[0091] The above specific embodiments do not constitute a limitation on the protection scope of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present application shall be included within the protection scope of the present application.

Claims

1. A message processing system, characterized in that, the system includes: A distribution configuration module: used to receive a message sent by a first service party, determine a message middleware corresponding to the event type according to the event type of the message sent by the first service party, and send the message sent by the first service party to the corresponding message middleware; A receiving configuration module: used to, in response to a receiving request sent by a second service party, determine a target message that the receiving request needs to receive; determine the target message middleware where the target message is located, obtain the target message from the target message middleware, and send the target message to the second service party.

2. The message processing system according to claim 1, characterized in that, the system further includes a processing configuration module, and the processing configuration module is used for: In response to the receiving request sent by the second service party, determine the target message that the receiving request needs to receive; Determine a processing method corresponding to the target message based on pre-set processing configuration information; Send the processing method to the second service party.

3. The message processing system according to claim 2, characterized in that, the distribution configuration module is further used for: Receive a new message obtained after the second service party processes the target message based on the processing method; Determine a new message middleware corresponding to the event type of the new message according to the event type of the new message, and send the new message to the new message middleware.

4. The message processing system according to claim 1, characterized in that, the distribution configuration module is further used for: Determine different event messages according to the event type of the message sent by the first service party, where the event messages are at least one; Respectively determine the message middleware corresponding to each event message; Send each event message to the corresponding message middleware.

5. A message processing method based on the message processing system according to claim 1, characterized in that, the method includes: Receive a message sent by a first service party, determine a message middleware corresponding to the event type according to the event type of the message sent by the first service party, and send the message sent by the first service party to the corresponding message middleware; In response to a receiving request sent by a second service party, determine a target message that the receiving request needs to receive; Determine the target message middleware where the target message is located, obtain the target message from the target message middleware, and send the target message to the second service party.

6. The message processing method according to claim 5, characterized in that, the method further includes: In response to the receiving request sent by the second service party, determine the target message that the receiving request needs to receive; Determine a processing method corresponding to the target message based on pre-set processing configuration information; Send the processing method to the second service party.

7. The message processing method according to claim 6, characterized in that, the method further includes: Receive a new message obtained after the second service party processes the target message based on the processing method; Determine a new message middleware corresponding to the event type of the new message according to the event type of the new message, and send the new message to the new message middleware.

8. The message processing system according to claim 5, wherein, receiving the message sent by the first service party, determining a message middleware corresponding to the event type according to the event type of the message sent by the first service party, and sending the message sent by the first service party to the corresponding message middleware, includes: determining different event messages according to the event type of the message sent by the first service party, wherein the event messages are at least one; respectively determining a message middleware corresponding to each event message; sending each event message to the corresponding message middleware.

9. A computer device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein, the memory stores computer instructions executable by the at least one processor, and the computer instructions are executed by the at least one processor so that the at least one processor can execute the method according to any one of claims 5-7.

10. A computer-readable storage medium, on which computer instructions are stored, wherein, the computer instructions are used to cause a computer to execute the method according to any one of claims 5 to 7.

Images