redis delay queue

redis delay queue

Introduction

We are usually used to using Rabbitmq and Kafka as message queue middleware to add asynchronous messaging between applications.Both of these middleware are professional message queue middleware with more features than most people can understand.

Students who have used Rabbitmq know how complicated it is to use. Before sending a message, you need to create a Exchange, and then create a Queue.Bind Queue and Exchange through a certain rule, specify routingkey when sending a message, and control the header information.Consumers also need to go through the above series of cumbersome processes before consuming messages.But in most cases, although our message queue has only one set of consumers, it still needs to go through the above tedious processes.

With Redis, it can free us. For those message queues with only one set of consumers, Redis can be used very easily.The message queue of Redis is not a professional message queue. It does not have many advanced features, and there is no ack guarantee. If you have the ultimate pursuit of message reliability, then it is not suitable for use.

Asynchronous message queue

Redis's list (list) data structure is often used as an asynchronous message queue, using rpush/lpush operations to enter the queue, and use lpop and rpop to exit the queue.

127.0.0.1:6379> lpush notfily-queue apple banana pear(integer) 3127.0.0.1:6379>llen notfily-queue(integer) 3127.0.0.1:6379>lpop notfily-queue"apple"127.0.0.1:6379>llen notfily-queue(integer) 2127.0.0.1:6379>lpop notfily-queue"pear"127.0.0.1:6379>lpop notfily-queue"banana"127.0.0.1:6379>lpop notfily-queue(nil)127.0.0.1:6379>llen notfily-queue(integer) 0