A database-based lightweight message queue implementation method and storage device

Abstract

The invention relates to the technical field of message processing, in particular to a method for implementing a lightweight message queue based on a database and a storage device. The method for implementing a lightweight message queue based on a database includes the steps of: creating a database table; receiving a request operation, and updating the message table according to the request operation; starting a local message listening program, and if there is an unprocessed message detected, then Write the consumption occupancy mark in the database for the corresponding unprocessed message; push the marked message to the local consumption queue; start the local consumption thread, monitor the local consumption queue, if there is a message to be consumed, obtain the message and consume it; After the consumption is over, update the message status. The technical scheme of the present invention adopts a message processing method based on a database table, and the entire message production and consumption process does not need to use MQ middleware as a medium, which reduces various configuration requirements of the hardware environment and system environment, and realizes the function of a lightweight message queue .

Description

technical field [0001] The invention relates to the technical field of message processing, in particular to a method for implementing a lightweight message queue based on a database and a storage device. Background technique [0002] The traditional message consumption model relies on MQ message middleware for implementation: the producer program produces messages and puts them into the specified queue, and then the consumer program pulls messages from the specified queue for consumption, and at the same time monitors the consumption process through logs Record, follow-up related message tracking based on the log. Such a consumption model has the following disadvantages: [0003] 1. The production environment must install and configure the corresponding MQ middleware products, which have higher requirements for software and hardware environment, procurement cost, compatibility, etc.; [0004] 2. The messages in MQ products are usually temporarily stored in the memory. If t...

AI Technical Summary

Problems solved by technology

[0003] 1. The production environment must install and configure the corresponding MQ middleware products, which have higher requirements for software and hardware environment, procurement cost, compatibility, etc.;

[0004] 2. The messages in MQ products are usually temporarily stored in the memory. If the queue application goes down, the messages will be at risk of being lost; and most of them can only use the built-in management page to browse the messages in the queue, which can only meet the universal monitoring Requirements, it is impossible to visually display the specific content of the message, key data items, processing status, etc., and it is not convenient for personalized monitoring of the message;

[0005] 3. The messages in the MQ product are destroyed after consumption, and it is difficult to realize the problems of message recurrence, abnormal traceability, and message re-consumption;

[0006] 4. The same message in the MQ product is difficult to be consumed by multiple businesses, and it is difficult to adapt to complex business scenarios and business functions

Images