CN112527525B - Distributed event bus processing method, terminal and medium based on message queue - Google Patents
Distributed event bus processing method, terminal and medium based on message queue Download PDFInfo
- Publication number
- CN112527525B CN112527525B CN202011459468.9A CN202011459468A CN112527525B CN 112527525 B CN112527525 B CN 112527525B CN 202011459468 A CN202011459468 A CN 202011459468A CN 112527525 B CN112527525 B CN 112527525B
- Authority
- CN
- China
- Prior art keywords
- message
- event
- node
- consumer
- middleware
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 15
- 238000000034 method Methods 0.000 claims abstract description 19
- 238000012795 verification Methods 0.000 claims abstract description 5
- 238000012545 processing Methods 0.000 claims description 30
- 230000002159 abnormal effect Effects 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 6
- 238000005538 encapsulation Methods 0.000 claims description 4
- 230000005856 abnormality Effects 0.000 claims description 2
- 230000000694 effects Effects 0.000 abstract description 2
- 230000008569 process Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000000903 blocking effect Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000005192 partition Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005316 response function Methods 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/548—Queue
Abstract
The application relates to the technical field of computers and aims at providing a distributed event bus processing method, a terminal and a medium based on a message queue, wherein the method comprises the steps of establishing connection with a publisher to acquire a published event message; performing basic attribute verification of event data on the acquired event message to generate a unique event ID; selecting available nodes from the node pool, and pushing the message to the message middleware; after receiving the subscription event request message of the consumer, decoding the subscription event request message, checking the validity of the event data and obtaining the event ID; establishing connection with the message middleware, subscribing the message middleware to a related message queue according to the event ID, and establishing a callback processor; and acquiring an event of the callback processor to receive the message of the message middleware, decoding the message, converting the message into a subscribed event structure, and pushing the event structure to a consumer by an event message stream. The method and the device have the effect of realizing the lightweight operation of the client.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, a terminal, and a medium for processing a distributed event bus based on a message queue.
Background
Currently, in distributed event bus systems, there are a number of scenarios that use message middleware to decouple application logic to deliver messages in different applications. Message middleware enables expanding inter-process communication in a distributed environment by providing a messaging and message queuing model. The message middleware utilizes an efficient and reliable message passing mechanism for platform-independent data communication and for integration of the distributed system based on the data communication. Message middleware supports synchronous mode and asynchronous mode, and asynchronous middleware has stronger fault tolerance than synchronous middleware, so that the message middleware is more widely used. The publish-subscribe interface of the asynchronous middleware can specify which type of user can accept which type of message, is more targeted, and becomes an informal standard of the asynchronous middleware.
However, many message middleware is composed of several components, so that the client needs to know the functions and the use modes of different components when using the middleware, and meanwhile, when using the middleware, the client needs to pay attention to details of routing, partitioning and the like of different events, namely, an interface based on event bus semantics, which is easy to configure and use, is not provided for the client, and the operation of the client is complicated.
With respect to the related art in the foregoing, the applicant believes that there is a defect that the existing message middleware does not provide an interface based on event bus semantics for the client, which is easy to configure and use, and the operation of the client is cumbersome.
Disclosure of Invention
In order to realize lightweight operation of a client, an interface based on event bus semantics, which is easy to configure and use, is provided for the client, and the application provides a distributed event bus processing method, a terminal and a medium based on a message queue.
The first object of the present application is to provide a distributed event bus processing method based on a message queue, which has the characteristics of easy configuration and use of a client.
The first object of the present application is achieved by the following technical solutions:
a distributed event bus processing method based on message queue establishes connection with a publisher to obtain event messages which are published by the publisher and formed by event data coding and encapsulation;
performing basic attribute verification of event data on the acquired event message to generate a unique event ID;
selecting available nodes from the node pool, delivering the event message to the message middleware, returning an event ID corresponding to the event message to the message middleware, and pushing the message to the message middleware;
after receiving the subscription event request message of the consumer, decoding the subscription event request message, checking the validity of the event data and obtaining the event ID;
establishing connection with the message middleware, subscribing the message middleware to a related message queue according to the event ID, and establishing a callback processor;
and acquiring an event of the callback processor to receive the message of the message middleware, decoding the message, converting the message into a subscribed event structure, and pushing the event structure to a consumer by an event message stream.
By adopting the technical scheme, the publisher encodes and encapsulates the event data to form an event message, and publishes the event; after an event is released by a releasing party, a server acquires an event message of the releasing party, performs parameter verification and generates a unique event ID, selects an available node from a node pool, delivers the event message to a message middleware, returns the event ID corresponding to the event message to the message middleware, pushes the message to the message middleware, so that complex operation is carried out on the server, and hides complex internal message routing for a client, so that details of event data are packaged, the client does not need to pay attention to details such as routing, partition and the like of different events, and the configuration and use of the client are easy; after a consumer requests to subscribe an event, a server receives and decodes a subscription message request, checks the validity of event data, establishes connection with a message middleware to subscribe the message queue related to the message middleware, establishes a callback processor, acquires an event of the callback processor to receive the message of the message middleware, decodes the message, converts the message into a subscribed event structure, pushes an event message stream to the consumer, stores and distributes the message according to the capability provided by the used message queue, and a client only processes delivery and consumption of the message.
The present application may be further configured in a preferred example to: the specific steps for selecting the available nodes from the node pool are as follows:
determining a next node from the recorded node offset delivered last time;
finding out a determined node from the node pool, and sending a ping message;
and when the node state information feedback exists, determining the node as an available node, and selecting the node.
By adopting the technical scheme, the information of the next node is determined from the recorded node offset delivered last time, so that the node can be found from the node pool and the availability detection can be carried out; when the node state information is fed back, the node is determined to be an available node, the operation of selecting the available node from the node pool is completed, and invalid event delivery is avoided.
The present application may be further configured in a preferred example to: when no node state information feedback exists after the ping message is sent, determining that the node is an abnormal node; continuing to offset from the recorded last delivered node to determine a new next node;
and finding out a newly determined node from the node pool and sending a ping message until the node state information is fed back.
By adopting the technical scheme, the node selected from the node pool is ensured to be an available node, and invalid event delivery is avoided.
The present application may be further configured in a preferred example to: when all nodes in the node pool have no node state information feedback, and after the node is deviated from the recorded last delivered node, no new next node exists, namely, the system is judged to be abnormal, and the delivery message is terminated.
By adopting the technical scheme, when the server side finds out the system is abnormal, the message delivery is terminated in time so as to reduce the burden of the system.
The present application may be further configured in a preferred example to: the subscription request message of the consumer includes the ID of the client and a list of event types to subscribe to.
By adopting the technical scheme, the subscription request message of the consumer comprises the ID of the consumer and the event type list to be subscribed, so that the subscription request of the consumer can be represented, and the server can distinguish the subscription requests of different consumers.
The present application may be further configured in a preferred example to: the event which is called back to the processor is obtained after discarding the event which is not interested by the consumer according to the subscription event request of the consumer.
By adopting the technical scheme, the callback processor discards the events which are not interested by the consumer according to the subscription event request of the consumer so as to acquire the events subscribed by the consumer, and performs event processing on the request based on the event bus.
The present application may be further configured in a preferred example to: after the event message stream is pushed to the consumer, a result of service logic processing after the consumer receives the event is obtained, and whether the event processing needs to be retried is judged.
By adopting the technical scheme, after the event message stream is pushed, whether the event processing needs to be retried is judged according to feedback of service logic processing results after the event is received by a consumer, so that successful pushing of the event is ensured, and the event pushing success probability is improved.
The present application may be further configured in a preferred example to: there are at least four message queues, and different message queues can provide different characteristics.
By adopting the technical scheme, when needed, the specific requirements are met by selecting the capability provided by different message queues, and the method is flexible to use and high in applicability.
The second purpose of the application is to provide an intelligent terminal, which has the characteristics of realizing the lightweight operation of the client and providing an event bus semantic interface based on which the client is easy to configure and use.
The second object of the present application is achieved by the following technical solutions:
an intelligent terminal comprises a memory and a processor, wherein the memory stores a computer program which can be loaded by the processor and execute the distributed event bus processing method based on the message queue.
The third object of the present application is to provide a computer readable storage medium, which has the characteristics of realizing the lightweight operation of a client, and providing an event bus semantic interface based on which the client is easy to configure and use.
The third object of the present application is achieved by the following technical solutions:
a computer readable storage medium storing a computer program capable of being loaded by a processor and executing the above-described message queue-based distributed event bus processing method.
In summary, the present application includes at least one of the following beneficial technical effects:
1. the distributed event bus processing method based on the message queue is characterized in that complex operation is carried out on a server side, the storage and the distribution of the message depend on the providing capability of the used message queue, a client side only processes the delivery and consumption of the message, other logics are packaged on the server side, the complexity of event processing based on message middleware is reduced, the lightweight of the operation of the client side is realized, an interface based on event bus semantics which is easy to configure and use is provided for the client side, the operation of the client side is easy, and the distributed event bus processing method based on the message queue is realized;
2. finding the next node from the node pool and carrying out availability detection to avoid invalid event delivery;
3. when all nodes in the node pool have no node state information feedback and are deviated from the recorded last delivered node, a new next node does not exist, namely, the system is judged to be abnormal, the delivery message is terminated, and the system load is reduced;
4. the subscription request message of the consumer comprises an ID of the consumer and an event type list to be subscribed to, so that the subscription request of the consumer is characterized, and the service side can distinguish the subscription requests of different consumers;
5. the callback processor discards the events which are not interested by the consumer according to the subscription event request of the consumer so as to acquire the events subscribed by the consumer, and performs event processing on the request based on an event bus;
6. the service end judges whether to retry event processing according to feedback of service logic processing results after receiving the event by the consumer so as to ensure successful pushing of the event and improve the success probability of event pushing;
7. at least four message queues are provided, and different message queues can provide different characteristics; when needed, the capability provided by different message queues is selected to meet specific requirements, so that the device is flexible to use and high in applicability.
Drawings
FIG. 1 is a schematic overall flow diagram of one embodiment of the present application.
Fig. 2 is a schematic diagram of an interaction flow between a server and a publisher in the present application.
Fig. 3 is a schematic diagram of an interaction flow between a server and a consumer in the present application.
Fig. 4 is a flow chart of a service end polling selection message queue node of the present application.
Detailed Description
The present application is described in further detail below with reference to the accompanying drawings.
The present embodiment is merely illustrative of the present application and is not intended to be limiting, and those skilled in the art, after having read the present specification, may make modifications to the present embodiment without creative contribution as required, but is protected by patent laws within the scope of the claims of the present application.
The embodiment of the application provides a distributed event bus processing method based on a message queue, which comprises the steps that an issuer issues an event; the server side polls and selects the message queue node until the message queue node is an available node; the service end selects the available node and pushes the message to the message middleware; when a consumer requests to subscribe to a message, a server subscribes a related message queue to a message middleware, and the message middleware pushes the message to the server; the server decodes the message, converts the message into a subscribed event structure, establishes connection through a subscription request and pushes the connection to the consumer.
The event bus mode is one of observer design modes, and the working components of the event bus mode are mainly divided into four types of event sources, event listeners, channels and event buses. When the event source is in operation, the generated information is sent to a specific channel of the event bus, the event monitor is subscribed to different channels in the event bus in advance to distinguish the response of the information, when the information is sent to the specific channel of the transaction bus, the corresponding event monitor monitors the information, and then the event monitor is executed according to the response function set in the program.
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
In addition, the term "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In this context, unless otherwise specified, the term "/" generally indicates that the associated object is an "or" relationship.
Embodiments of the present application are described in further detail below with reference to the drawings attached hereto.
The embodiment of the application provides a distributed event bus processing method based on a message queue, and the main flow of the method is described as follows.
Referring to fig. 1 and 2, the server and the publisher interact through a custom gRPC interface. Specifically, the publisher interacts with the server through the publishing interface to publish the event.
When the publisher encodes the event data with protobuf, the event data is encapsulated into a message structure of gRPC interface, and the event is published.
The server establishes HTTP/2 connection with the publisher through gRPC interface to obtain event message published by the publisher.
After receiving the event message, the server performs basic attribute verification of the event data on the event message, generates a unique event ID, and encodes the event data into a NSQ message structure.
The server polls and selects the message queue node until the message queue node is a surviving node, i.e. the node is determined to be an available node.
The service end selects the available node from the node pool, delivers the message structure of NSQ to the message middleware, returns the event ID corresponding to the event message to the message middleware, pushes the message to the message middleware, and returns the event ID to the publisher through the gRPC interface message.
Referring to fig. 1 and 3, the server and the consumer interact through a custom gRPC interface. Specifically, the consumer interacts with the server through the subscore interface to Subscribe to the event.
The consumer establishes HTTP/2 connection with the server through gRPC interface, and requests subscription information from the server, wherein the subscription information comprises ID of the consumer and event type list to be subscribed. The consumer informs the server of the ID of the consumer and the event type list to be subscribed.
After receiving the subscription information, the server decodes the subscription request information, checks the validity of the event data and acquires the event ID.
The server establishes connection with the message middleware, subscribes the message middleware to the related message queue according to the event ID, and establishes a callback processor. When receiving the message push of the server, the callback processor picks the event type subscribed by the consumer and discards the event which is not interested.
The server acquires the event received by the callback processor to receive the message of the message middleware, decodes the message, converts the message into an event structure subscribed by the consumer, and pushes the event structure to the consumer through the gRPC interface flow.
The consumption pattern of at least one and at most one time is dependent on the capabilities provided by the message queue used.
After receiving the event, the consumer performs service logic processing, and responds to the processing result of the server with AckReq.
The server decides whether to need to retry event processing according to the processing result of AckReq.
When the event processing needs to be retried, the server side continues to acquire the event received by the callback processor so as to receive the message of the message middleware, decodes the message, converts the message into an event structure subscribed by the consumer, and pushes the event structure to the consumer through the gRPC interface flow until the processing result of the AckReq does not need to retry the event processing. The subscore interface relies on exceptions to the business logic to determine if the event was successfully handled. When an abnormality occurs, the event has the opportunity of retry, and idempotent processing is needed in the business logic.
The subscore interface is implemented using bi-directional streaming of the grpc interface. In order to simplify the internal processing logic of the consumer, a request/response mode is used on the protocol, and in the event stream processing process, the next event needs to be processed continuously after waiting for the response of the last event, so that the parallelism of event processing is limited, and the event processing is orderly performed. The developer may also use different threads for different events to increase the throughput of parallel processing.
In this embodiment, both the publisher and the consumer are clients.
Referring to fig. 4, the specific step of the server side polling the selected message queue node includes determining the next node from the recorded last delivered node offset, selecting the next node from the NSQ node pool, and sending a ping message to determine whether the node survives.
After sending the ping message, the server receives the feedback of the state information of the node, and the node survives to determine that the node is an available node.
When no node state information feedback exists after the ping message is sent, the server determines that the node is an abnormal node. The server continues to shift from the recorded last delivered node to determine a new next node. The server finds out the newly determined node from the node pool and sends a ping message until the state information of the node is fed back to the server, determines the node as an available node, and selects the node.
When no node state information feedback exists after the ping message is sent and the node is offset from the recorded last delivered node, and the next node cannot be determined, namely, all nodes in the node pool try and no node state information feedback exists after the node pool try, namely, the system is judged to be abnormal, and the server ends to deliver the message to the message middleware.
Further, the server may be compatible with multiple message queues. In this embodiment, the number of message queues may be four, and different message queues can provide different characteristics. The capabilities provided by the different message queues may be selected to meet specific needs when needed, such as some message queues supporting transactional message delivery and consumption and some message queues supporting delayed consumption messages.
The capability provided by the message queue is implemented by the interface set. In this embodiment, there are four public interfaces, which are a blocking type non-delay public interface, a blocking type supporting delay event public interface, an asynchronous non-delay public interface, and an asynchronous supporting delay event public interface, respectively, to provide support for delay delivery events. The blocking event interface is suitable for being called in a transaction block, namely a database transaction logic block of an application layer, so that the data consistency of cross-service is ensured to a great extent. The asynchronous event interface ensures that the execution of the internal logic is not interrupted and the inner layer call is not influenced through the grpc interface because the end of the external call logic or the early termination cannot cause the event to be terminated.
When in use, whether the asynchronous interface is used or not is selected according to the use scene. In particular, the available use of asynchronous interfaces that are sensitive to interface response speed; the available use of synchronization interfaces that are sensitive to data consistency.
The present embodiment provides the basic message partition capability by utilizing the extensibility of the existing message middleware, and at the same time, the extensibility can be further performed when the characteristics of the interface are not satisfied.
The embodiment of the application also provides an intelligent terminal, which comprises a memory and a processor, wherein the memory stores a computer program which can be loaded by the processor and execute the distributed event bus processing method based on the message queue.
Specifically, connection is established with the publisher, and an event message which is formed by event data coding and encapsulation and published by the publisher is obtained.
And checking the basic attribute of the event data of the acquired event message to generate a unique event ID.
And selecting available nodes from the node pool, delivering the event message to the message middleware, returning an event ID corresponding to the event message to the message middleware, and pushing the message to the message middleware.
After receiving the subscription event request message of the consumer, decoding the subscription event request message, checking the validity of the event data and acquiring the event ID.
And establishing connection with the message middleware, subscribing the message middleware to a related message queue according to the event ID, and establishing a callback processor.
And acquiring an event of the callback processor to receive the message of the message middleware, decoding the message, converting the message into a subscribed event structure, and pushing the event structure to a consumer by an event message stream.
Further, the embodiment of the application also provides a computer readable storage medium, which stores a computer program capable of being loaded by a processor and executing the distributed event bus processing method based on the message queue. The computer-readable storage medium includes, for example: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Specifically, connection is established with the publisher, and an event message which is formed by event data coding and encapsulation and published by the publisher is obtained.
And checking the basic attribute of the event data of the acquired event message to generate a unique event ID.
And selecting available nodes from the node pool, delivering the event message to the message middleware, returning an event ID corresponding to the event message to the message middleware, and pushing the message to the message middleware.
After receiving the subscription event request message of the consumer, decoding the subscription event request message, checking the validity of the event data and acquiring the event ID.
And establishing connection with the message middleware, subscribing the message middleware to a related message queue according to the event ID, and establishing a callback processor.
And acquiring an event of the callback processor to receive the message of the message middleware, decoding the message, converting the message into a subscribed event structure, and pushing the event structure to a consumer by an event message stream.
The beneficial effects of the embodiment of the application are as follows:
1. the complex operation is carried out on the server, and the complex internal message route is hidden from the client, so that details of event data are encapsulated, the client does not need to pay attention to details of routes, partitions and the like of different events, and the configuration and the use of the client are easy; meanwhile, the storage and distribution of the messages depend on the providing capability of the used message queues, the client only processes the delivery and consumption of the messages, other logics are packaged at the server, the complexity of event processing based on message middleware is reduced, the lightweight of the client operation is realized, an interface based on event bus semantics, which is easy to configure and use, is provided for the client, the client operation is easy, and the distributed event bus processing based on the message queues is realized;
2. the server can be compatible with a plurality of message queues, and different message queues can provide different characteristics; when needed, the capability provided by different message queues can be selected to meet specific requirements, and the method is flexible to use and high in applicability.
Claims (9)
1. A distributed event bus processing method based on message queue is characterized in that,
establishing connection with a publisher to obtain an event message which is published by the publisher and formed by event data coding and encapsulation;
performing basic attribute verification of event data on the acquired event message to generate a unique event ID;
selecting available nodes from the node pool, delivering the event message to the message middleware, returning an event ID corresponding to the event message to the message middleware, and pushing the message to the message middleware;
after receiving the subscription event request message of the consumer, decoding the subscription event request message, checking the validity of the event data and obtaining the event ID;
establishing connection with the message middleware, subscribing the message middleware to a related message queue according to the event ID, and establishing a callback processor;
acquiring an event of a callback processor to receive a message of a message middleware, decoding the message, converting the message into a subscribed event structure, and pushing the event structure to a consumer by an event message stream;
the specific steps of selecting the available nodes from the node pool are as follows:
determining a next node from the recorded node offset delivered last time;
finding out a determined node from the node pool, and sending a ping message;
and when the node state information feedback exists, determining the node as an available node, and selecting the node.
2. A method for message queue based distributed event bus processing as defined in claim 1, wherein,
when no node state information feedback exists after the ping message is sent, determining that the node is an abnormal node; continuing to offset from the recorded last delivered node to determine a new next node;
and finding out a newly determined node from the node pool and sending a ping message until the node state information is fed back.
3. The method for processing a distributed event bus based on a message queue as set forth in claim 2, wherein when all nodes in the node pool have no node status information feedback and are shifted from the last time the node that has been posted is recorded, no new next node is determined as a system abnormality, and the posted message is terminated.
4. The method of claim 1, wherein the subscription request message of the consumer includes an ID of the client and a list of event types to be subscribed to.
5. The method of claim 1, wherein the event is received back from the processor after discarding the event not of interest to the consumer based on a subscription event request from the consumer.
6. The method for processing a distributed event bus based on a message queue according to claim 1, wherein after the event message stream is pushed to the consumer, a result of service logic processing performed after the consumer receives the event is obtained, and whether the event processing needs to be retried is determined.
7. A method of handling a distributed event bus based on message queues according to claim 1, wherein there are at least four message queues, different message queues providing different characteristics.
8. An intelligent terminal comprising a memory and a processor, wherein the memory has stored thereon a computer program that can be loaded by the processor and perform the method according to any of claims 1 to 7.
9. A computer readable storage medium, characterized in that a computer program is stored which can be loaded by a processor and which performs the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011459468.9A CN112527525B (en) | 2020-12-11 | 2020-12-11 | Distributed event bus processing method, terminal and medium based on message queue |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011459468.9A CN112527525B (en) | 2020-12-11 | 2020-12-11 | Distributed event bus processing method, terminal and medium based on message queue |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112527525A CN112527525A (en) | 2021-03-19 |
| CN112527525B true CN112527525B (en) | 2024-04-02 |
Family
ID=74999201
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011459468.9A Active CN112527525B (en) | 2020-12-11 | 2020-12-11 | Distributed event bus processing method, terminal and medium based on message queue |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112527525B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113098969B (en) * | 2021-04-09 | 2022-12-20 | 薪得付信息技术(上海)有限公司 | Data distribution method, device and system and electronic equipment |
| CN113489756A (en) * | 2021-07-23 | 2021-10-08 | 中企云链（北京）金融信息服务有限公司 | Internet of things distributed event-driven service system |
| CN113742075B (en) * | 2021-09-07 | 2024-04-09 | 北京百度网讯科技有限公司 | Task processing method, device and system based on cloud distributed system |
| CN114257638A (en) * | 2021-12-23 | 2022-03-29 | 思必驰科技股份有限公司 | Information manager, information transfer management method, electronic device, and storage medium |
| CN115016954B (en) * | 2021-12-24 | 2023-03-24 | 荣耀终端有限公司 | Event message management method, electronic device and computer readable storage medium |
| CN114629904A (en) * | 2022-02-15 | 2022-06-14 | 广州伊智信息科技有限公司 | Distributed event processing method, system, device and medium |
| CN114579493A (en) * | 2022-03-03 | 2022-06-03 | 夏春萌 | Mechanism for reducing software coupling degree through software type data interaction bus |
| CN115118772A (en) * | 2022-06-21 | 2022-09-27 | 壹沓科技(上海)有限公司 | Message communication system and method |
| CN115150465A (en) * | 2022-07-08 | 2022-10-04 | 中国建设银行股份有限公司 | Information processing method, device, equipment, storage medium and product |
| CN115623019B (en) * | 2022-12-02 | 2023-03-21 | 杭州雅拓信息技术有限公司 | Distributed operation flow scheduling execution method and system |
| CN115936735B (en) * | 2023-02-15 | 2023-06-16 | 深圳市思为软件技术有限公司 | Event processing method and device based on event validity verification |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101251797A (en) * | 2008-03-31 | 2008-08-27 | 中国船舶重工集团公司第七〇九研究所 | Element real time initiative transferring method based on domain model |
| CN102055644A (en) * | 2009-11-11 | 2011-05-11 | 中兴通讯股份有限公司 | Method, device and system for load management in distributed directory service system |
| CN103763378A (en) * | 2014-01-24 | 2014-04-30 | 中国联合网络通信集团有限公司 | Task processing method and system and nodes based on distributive type calculation system |
| WO2016007679A1 (en) * | 2014-07-08 | 2016-01-14 | Pneuron Corp. | Virtualized execution across distributed nodes |
| CN107766129A (en) * | 2016-08-17 | 2018-03-06 | 北京金山云网络技术有限公司 | A kind of task processing method, apparatus and system |
| CN108196961A (en) * | 2017-12-28 | 2018-06-22 | 广东蜂助手网络技术股份有限公司 | A kind of asynchronous message processing method, terminal, system and storage medium |
| CN110191164A (en) * | 2019-05-20 | 2019-08-30 | 中国工商银行股份有限公司 | Distributed Services access system and method |
| CN110968586A (en) * | 2018-09-30 | 2020-04-07 | 北京国双科技有限公司 | Distributed transaction processing method and device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7406537B2 (en) * | 2002-11-26 | 2008-07-29 | Progress Software Corporation | Dynamic subscription and message routing on a topic between publishing nodes and subscribing nodes |
| US11385944B2 (en) * | 2017-07-10 | 2022-07-12 | Nokia Solutions And Networks Oy | Event handling in distributed event handling systems |
-
2020
- 2020-12-11 CN CN202011459468.9A patent/CN112527525B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101251797A (en) * | 2008-03-31 | 2008-08-27 | 中国船舶重工集团公司第七〇九研究所 | Element real time initiative transferring method based on domain model |
| CN102055644A (en) * | 2009-11-11 | 2011-05-11 | 中兴通讯股份有限公司 | Method, device and system for load management in distributed directory service system |
| CN103763378A (en) * | 2014-01-24 | 2014-04-30 | 中国联合网络通信集团有限公司 | Task processing method and system and nodes based on distributive type calculation system |
| WO2016007679A1 (en) * | 2014-07-08 | 2016-01-14 | Pneuron Corp. | Virtualized execution across distributed nodes |
| CN107766129A (en) * | 2016-08-17 | 2018-03-06 | 北京金山云网络技术有限公司 | A kind of task processing method, apparatus and system |
| CN108196961A (en) * | 2017-12-28 | 2018-06-22 | 广东蜂助手网络技术股份有限公司 | A kind of asynchronous message processing method, terminal, system and storage medium |
| CN110968586A (en) * | 2018-09-30 | 2020-04-07 | 北京国双科技有限公司 | Distributed transaction processing method and device |
| CN110191164A (en) * | 2019-05-20 | 2019-08-30 | 中国工商银行股份有限公司 | Distributed Services access system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112527525A (en) | 2021-03-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112527525B (en) | Distributed event bus processing method, terminal and medium based on message queue | |
| US10244066B2 (en) | Push notification delivery system | |
| John et al. | A survey of distributed message broker queues | |
| US8452833B2 (en) | Cached message distribution via HTTP redirects | |
| US8136122B2 (en) | Systems and/or methods for providing feature-rich proprietary and standards-based triggers via a trigger subsystem | |
| CN111212085B (en) | Method for synchronously calling Internet of things platform, internet of things system and network equipment | |
| CN111711663A (en) | Processing method and device for publishing and subscribing services and electronic equipment | |
| US7921427B2 (en) | Method and system for processing messages in an application cluster | |
| US8037153B2 (en) | Dynamic partitioning of messaging system topics | |
| CN114363407B (en) | Message service method and device, readable storage medium and electronic equipment | |
| US20130086154A1 (en) | System and method for providing asynchrony in web services | |
| CN110413822B (en) | Offline image structured analysis method, device and system and storage medium | |
| CN110753129A (en) | Message transmission method, system, device, equipment and computer readable storage medium | |
| CN110727507B (en) | Message processing method and device, computer equipment and storage medium | |
| CN113064740A (en) | Message processing method and device | |
| CN113965628A (en) | Message scheduling method, server and storage medium | |
| US11372849B2 (en) | Transaction confirmation methods and apparatuses in blockchain network | |
| CN115334155A (en) | Message queue agent method and device | |
| CN112596933B (en) | Micro-service system based on message event communication | |
| CN110162415B (en) | Method, server, device and storage medium for processing data request | |
| CN114116247A (en) | Redis-based message processing method, device, system, server and medium | |
| CN112686599A (en) | Request response method, device, system, electronic equipment and computer readable medium | |
| CN112866622A (en) | Information processing method, device, server, storage medium and system | |
| JP4647511B2 (en) | Asynchronous message processing system and asynchronous message processing program | |
| CN112783925B (en) | Paging retrieval method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |