CN103927218B - Event distributing method and system - Google Patents

Abstract

The invention relates to an event distribution method and system. The method includes: the message queue cluster receives the registered event from the management server and the subscription configuration information generated by the user's subscription operation; the proxy server actively pulls and saves all event information in the message queue cluster; the execution server actively pulls All subscription configuration information in the message queue cluster is saved; the proxy server receives the event message initiated by the user, and pushes the event message to the corresponding message queue server according to the binding information between the event and the message queue server; the execution server is in The event message is pulled from the message queue cluster, and the event message is concurrency controlled and sent to the event processing address according to the subscription configuration information. The invention simplifies the development of cross-system event message transmission, and event messages can be sent concurrently, thereby improving the processing efficiency of event messages.

Description

Event distribution method and system

technical field

The invention relates to the supporting business technology in the network, in particular to a technology for transmitting events and messages across systems.

Background technique

At present, events and messages across systems in many companies are often implemented manually. The synchronization method is simple and reliable, but it affects performance, and makes the primary and secondary business processes unclear, and the asynchronous method is complicated. No matter whether MQ (Message Queue) or Redis is used as the Message queues require scheduled task processing and complex and repetitive error handling processes. This manual implementation lacks unified event management and authority control, is messy and difficult to maintain, and has low efficiency in event message processing.

Contents of the invention

The purpose of the present invention is to propose an event distribution method, which can solve the problem of low efficiency of event message processing.

In order to achieve the above object, the technical scheme adopted in the present invention is as follows:

Event distribution method, which includes the following steps:

Step 1. The message queue cluster receives the registered event from the management server and the subscription configuration information generated by the user's subscription operation. The event is correspondingly bound to a message queue server in the message queue cluster. The subscription configuration information Including subscribed events, event processing concurrency and event processing address;

Step 2. The proxy server actively pulls and saves all event information in the message queue cluster;

Step 3. The execution server actively pulls and saves all subscription configuration information in the message queue cluster;

Step 4, the proxy server receives the event message initiated by the user, and pushes the event message to the corresponding message queue server according to the binding information between the event and the message queue server;

Step 5. The execution server pulls the event message from the message queue cluster, and performs concurrency control on the event message and sends it to the event processing address according to the subscription configuration information;

Wherein, the execution sequence of step 2 and step 3 is not limited.

Preferably, the events and subscription configuration information of message queue clusters in different computer rooms are actively synchronized in real time.

Preferably, in step 1, the registered event has an importance mark, and the importance mark includes a persistent mark and a non-persistent mark. Further preferably, in step 4, if the push of the event message fails, further judge the event importance mark corresponding to the event message, and if the importance mark is a persistent mark, then temporarily delete the event message Store it in its database and push it again, if the importance mark is a non-persistent mark, then discard the event message.

The present invention also proposes an event distribution system for implementing the above event distribution method, which includes the following devices:

The message middleware, which is set in the message queue cluster, is used to receive the registered event from the management server and the subscription configuration information generated by the user's subscription operation, and the event is correspondingly bound to a message queue server in the message queue cluster determined, the subscription configuration information includes subscribed events, event processing concurrency and event processing address;

The first pulling module, which is set on the proxy server, is used to actively pull and save all event information in the message queue cluster;

The second pulling module, which is set on the execution server, is used to actively pull and save all subscription configuration information in the message queue cluster;

A push module, which is set on the proxy server, is used to receive the event message initiated by the user, and push the event message to the corresponding message queue server according to the binding information of the event and the message queue server;

An execution module, which is set on the execution server, is used to pull the event message from the message queue cluster, and perform concurrency control on the event message and send it to the event processing address according to the subscription configuration information;

Wherein, the execution order of the first pulling module and the second pulling module is not limited.

Preferably, the events and subscription configuration information of message queue clusters in different computer rooms are actively synchronized in real time.

Preferably, in the message middleware, the registered event has an importance mark, and the importance mark includes a persistent mark and a non-persistent mark. Further preferably, in the push module, if the push of the event message fails, further judge the event importance mark corresponding to the event message, and if the importance mark is a persistent mark, temporarily store the event message Store it in its database and push it again, if the importance mark is a non-persistent mark, then discard the event message.

The present invention has following beneficial effect:

Simplifies the development of cross-system event messaging. Producers only need to subscribe to events on the management server and set subscription configuration information to implement the event message delivery system. The development efficiency is high, and event messages can be sent concurrently, thereby improving event message delivery. processing efficiency.

Description of drawings

Fig. 1 is a flow chart of the event distribution method of the preferred embodiment of the present invention;

Fig. 2 is a system architecture diagram of a specific example of an event distribution method in a preferred embodiment of the present invention.

detailed description

In the following, the present invention will be further described in conjunction with the drawings and specific embodiments.

As shown in Figure 1, an event distribution method includes the following steps:

Step S1, the message queue cluster receives the registered event from the management server and the subscription configuration information generated by the user's subscription operation, the event is bound to a message queue server in the message queue cluster, and the subscription configuration information Including subscribed events, number of concurrent event processing (for example, 5), and event processing address (that is, HTTP event processing URL). The management server can be managed by an administrator, adding an event (that is, the registration of the event), which corresponds to the message queue server and a brief description. When adding an event, an importance mark may be added according to the importance of the event, and the importance mark includes a persistent mark and a non-persistent mark, so as to improve data processing performance.

Step S2, the proxy server actively pulls and saves all event information in the message queue cluster. For the initialized proxy server, all event information in the message queue cluster is pulled. After initialization, if there is a new event, only the new event is pulled, and the new event is compared with the saved event. merge.

Step S3, the execution server actively pulls and saves all subscription configuration information in the message queue cluster. For the initialized execution server, all subscription configuration information in the message queue cluster is pulled. After initialization, if there is new subscription configuration information, only the new subscription configuration information is pulled, and the new subscription configuration The information is merged with the saved subscription configuration information.

Step S4, the proxy server receives the event message initiated by the user, and pushes the event message to the corresponding message queue server according to the binding information of the event and the message queue server. If the push of the event message fails, further judge the event importance mark corresponding to the event message, if the importance mark is a persistent mark, temporarily store the event message in its database and push it again , until the sending is successful, if the importance mark is a non-persistent mark, the event message is discarded, so as to ensure that the information cannot be lost and recovered, and the system processing performance is improved.

Step S5, the execution server pulls the event message from the message queue cluster, and performs concurrency control on the event message and sends it to the event processing address according to the subscription configuration information.

Wherein, the execution order of step S2 and step S3 is not limited, that is, step S2 may be executed before step S3, or step S3 may be executed before step S2, or step S2 and step S3 may be executed simultaneously.

In this embodiment, there are multiple message queue clusters, which are configured in different computer rooms, and the events and subscription configuration information of the message queue clusters in different computer rooms are actively synchronized in real time.

This embodiment also proposes an event distribution system for implementing the above event distribution method, which includes the following devices:

The message middleware, which is set in the message queue cluster, is used to receive the registered event from the management server and the subscription configuration information generated by the user's subscription operation, and the event is correspondingly bound to a message queue server in the message queue cluster determined, the subscription configuration information includes subscribed events, concurrent number of event processing and event processing address. Events and subscription configuration information of message queue clusters in different computer rooms are actively synchronized in real time. Registered events have importance marks, and the importance marks include persistent marks and non-persistent marks.

The first pulling module is set in the proxy server and is used to actively pull and store all event information in the message queue cluster.

The second pulling module is set on the execution server and is used to actively pull and save all subscription configuration information in the message queue cluster.

The push module is set on the proxy server and is used to receive the event message initiated by the user, and push the event message to the corresponding message queue server according to the binding information of the event and the message queue server. If the push of the event message fails, further judge the event importance mark corresponding to the event message, if the importance mark is a persistent mark, temporarily store the event message in its database and push it again , if the importance mark is a non-persistent mark, the event message is discarded.

The execution module is set on the execution server, and is used for pulling the event message from the message queue cluster, and performing concurrency control on the event message and sending it to the event processing address according to the subscription configuration information.

Wherein, the execution order of the first pulling module and the second pulling module is not limited.

As shown in FIG. 2 , it is a system architecture diagram of a specific application of this embodiment. Assume that machine room 1 and machine room 2 are included. Both computer rooms are equipped with message queue clusters, execution servers and proxy servers, and computer room 1 also has a management server. A message queue cluster includes multiple incremental message queue servers and multiple message queue servers. The functions of each device are as follows:

The management server server is used to connect to the message queue cluster, add, delete, modify and check the administrator registration event, send the event management information registered by the administrator to the incremental message queue server and link the registration event to the corresponding message queue server For binding, the incremental message queue server is a service for saving incremental events and incremental subscriptions. The message queue server corresponding to the registration event is used to save the messages sent by the user. An event subscribed by a user corresponds to a Adapted message queue server. The management server is also used to display and analyze the event status, mainly calling the http status code returned by the event processing URL, such as 200: the request is successful, 404: the corresponding interface is not found, 500: the interface is wrong, etc., and the event is at a certain moment The number of processing times and addresses, the administrator can analyze whether the event processing is successful, the number of requests, etc. The management server displays the operation contents in WEB pages.

The proxy server is used to connect to the message queue cluster. When starting the initialization, it will request the permission of the management server through http and obtain all event information, and save it in its memory; actively subscribe to the incremental message queue server, and after receiving the registered event information, Combined with all event information; persistent event refers to the attribute set by the administrator when registering the event, indicating that the event is a very important message to process. If the proxy server fails to catch an exception when sending the event message, it will be saved to the local database queue first , and send them one by one, and they can be restored.

The execution server is used to connect to the message queue cluster. When starting and initializing, it pulls all the subscription configuration information and actively subscribes to the incremental message queue server. After receiving the event message, the message is processed through the event processing URL of the event message set by the user on the management server. Processing; and has concurrency control function, through the maximum number of concurrency set by the user on the management server, and the management server as the master control center to perform logical operations on the current number of concurrency to control the number of processes that the execution server is processing events.

In fact, it also includes a client for receiving user operations and connecting with the management server through the proxy server.

In this embodiment, Rabbit MQ is used as the message middleware.

In this embodiment, the management server, the message queue cluster, the execution server, the proxy server, and the client are all connected through RPC (Remote Procedure Call Protocol, remote procedure call protocol).

For those skilled in the art, various other corresponding changes and modifications can be made according to the technical solutions and ideas described above, and all these changes and modifications should fall within the protection scope of the claims of the present invention.

Claims (6)

1. event distributing method, it is characterised in that comprise the following steps：

Step 1, message queue cluster receive the event of the registration from management server and are produced because of the subscription operation of user Subscription configuration information, the event carries out corresponding binding with a Message Queuing server in message queue cluster, described Subscribing to configuration information includes event, event handling number of concurrent and the event handling address subscribed to；

Whole event informations and preserved in step 2, proxy server active pull message queue cluster；

Whole subscription configuration informations and preserved in step 3, execute server active pull message queue cluster；

Step 4, proxy server receive Client-initiated event message, and are believed according to the binding of event and Message Queuing server Breath, corresponding Message Queuing server is pushed to by the event message；

Step 5, execute server pull the event message in message queue cluster, and according to configuration information is subscribed to, to institute Stating event message carries out con current control and sends to event handling address；

Wherein, the execution sequence of step 2 and step 3 is unrestricted；

The event and subscription configuration information of the message queue cluster of different computer rooms actively carry out real-time synchronization operation.

2. event distributing method as claimed in claim 1, it is characterised in that in step 1, the event of registration has importance degree Mark, the important scale designation includes persistence mark and non-persistentization mark.

3. event distributing method as claimed in claim 2, it is characterised in that in step 4, if the event message is pushed losing Lose, then event severity level mark corresponding with the event message is determined whether, if the importance degree is labeled as persistence mark Note, then keep in the event message into its database and pushed again, if the importance degree is labeled as non-persistentization Mark, then abandon the event message.

4. event distribution system, it is characterised in that including following device：

Message-oriented middleware, it is located at message queue cluster, for receiving the event of the registration from management server and because of user Subscription operation and the subscription configuration information that produces, the event enters with a Message Queuing server in message queue cluster Row correspondence binding, the configuration information of subscribing to includes event, event handling number of concurrent and the event handling address subscribed to；

First pulls module, and it is located at proxy server, for event information whole in active pull message queue cluster simultaneously Preserved；

Second pulls module, and it is located at execute server, and confidence is matched somebody with somebody for subscription whole in active pull message queue cluster Cease and preserved；

Pushing module, it is located at proxy server, for receiving Client-initiated event message, and according to event and message queue The binding information of server, corresponding Message Queuing server is pushed to by the event message；

Performing module, it is located at execute server, for pulling the event message in message queue cluster, and according to subscription Configuration information, con current control is carried out to the event message and is sent to event handling address；

Wherein, first pull module and second pull module execution sequence it is unrestricted；The message queue cluster of different computer rooms Event and subscribe to configuration information actively carry out real-time synchronization operation.

5. event distribution system as claimed in claim 4, it is characterised in that between in the message in part, the event of registration has Important scale designation, the important scale designation includes persistence mark and non-persistentization mark.

6. event distribution system as claimed in claim 5, it is characterised in that in pushing module, if the event message is pushed away Failure is sent, then event severity level mark corresponding with the event message is determined whether, if the importance degree is labeled as lasting Change mark, then the event message is kept in into its database and pushed again, if the importance degree is held labeled as non- Longization is marked, then abandon the event message.