Distributed event bus processing method based on message queue, terminal and medium

Abstract

The invention relates to the technical field of computers, and aims to provide a distributed event bus processing method based on a message queue, a terminal and a medium, and the method comprises thesteps: building connection with a publisher, and obtaining a published event message; performing basic attribute verification of event data on the obtained event message to generate a unique event ID; selecting available nodes from the node pool, and pushing messages to the message middleware; after a subscription event request message of a consumer is received, decoding the subscription event request message, verifying the legality of event data and obtaining an event ID; establishing connection with the message middleware, subscribing a related message queue to the message middleware according to the event ID, and establishing a callback processor; and acquiring an event of a callback processor to receive a message of the message middleware, decoding the message, converting the messageinto a subscribed event structure, and pushing the event message flow to a consumer. The method has the effect of realizing lightweight operation of the client.

Description

technical field [0001] The present application relates to the field of computer technology, in particular to a message queue-based distributed event bus processing method, terminal and medium. Background technique [0002] At present, in the distributed event bus system, there are a large number of scenarios where message middleware is used to decouple application logic to transmit messages in different applications. Messaging middleware implements communication between processes in a distributed environment by providing message passing and message queuing models. Message middleware utilizes an efficient and reliable message delivery mechanism for platform-independent data exchange, and integrates distributed systems based on data communication. Message middleware supports both synchronous and asynchronous methods. Because asynchronous middleware is more fault-tolerant than synchronous middleware, it is more widely used. The publish-subscribe interface of asynchronous midd...

AI Technical Summary

Problems solved by technology

[0003] However, many message middleware are composed of several components. When using them, the client needs to understand the functions and usage methods of different components. At the same time, when using these middleware, the client needs to pay attention to details such as routing and partitioning of different events. It does not provide an easy-to-configure and use interface based on event bus semantics for the client, and the operation of the client is cumbersome

[0004] In view of the related technologies mentioned above, the applicant believes that the existing message middleware does not provide the client with an interface based on event bus semantics that is easy to configure and use, and the client operation is cumbersome.

Images