A method, device and storage medium for sending and consuming mq messages

Abstract

The invention relates to the technical field of computers, and discloses a method, a device and a storage medium for sending and consuming MQ messages, and specifically discloses a method for sending and consuming MQ messages, which includes a sending step and a receiving step. The sending step includes: based on a service Build a message model; configure field parameters for the message model and send it through the sdk after encryption; the receiving step includes: initializing the message receiving component, decrypting the message model, and comparing whether the field parameters in the message model are consistent with the target field parameters of the current message receiving component, if If it is consistent, ack is returned to the sender, and the message consumption is successful. The present invention has at least the following beneficial effects: it can automatically identify and switch to the currently used message queue framework, can automatically identify and match the target microservice for message sending and the microservice for message consumption, improve the efficiency of message transmission and save resources, and ensure that Security of messaging.

Description

technical field [0001] The present invention relates to the field of computer technology, and in particular, to a method, device and storage medium for sending and consuming MQ messages. Background technique [0002] At present, asynchronous messages are widely used in business middle-end architecture, mainly for asynchronous decoupling, traffic peak shaving, cache synchronization, distributed transaction messages, etc. Usually, the message sender and the message receiver belong to different microservices. In actual use, in order to ensure that the target microservice that consumes the message corresponds to the target microservice that the sender sends the message, the existing operation is, for each Each set of microservices creates a new topic and queue. When more and more microservices participate in message sending and receiving, multiple topics and queues need to be created. Since each topic and queue need to be declared and bound on the cloud server and each topic an...

AI Technical Summary

Problems solved by technology

Usually, the message sender and message receiver belong to different microservices. In actual use, in order to ensure that the target microservice that consumes the message corresponds to the target microservice that the sender sends the message, the existing operation is, for each Each set of microservices creates a new topic and queue. When more and more microservices participate in message sending and receiving, multiple topics and queues need to be created. Because each topic and queue need to be declared and bound on the cloud server Each topic and queue must be configured in the configuration center according to different microservice environments. When there are more and more topics and queues, the maintenance work becomes more and more difficult. Based on the existing operation method, When there are more and more topics and queues, switching the Mq framework becomes more time-consuming and wastes limited resources. At the same time, based on the existing encryption method, when there are more and more topics and queues , the message may be acquired by other environments during the delivery process and cause the risk of leaking the content of the message

Images