Shulou(Shulou.com)06/01 Report--

What is a redis message queue? This problem may be often seen in our daily study or work. I hope you can gain a lot from this question. The following is the reference content that the editor brings to you, let's take a look at it!

Queue

Is a special linear table, the special feature is that it only allows delete operations at the front end of the table (front), and insert operations at the back end of the table (rear). Like the stack, a queue is a linear table with limited operations. The end of the insert operation is called the end of the queue, and the end of the delete operation is called the head of the line.

Message queue

Is a container that holds a message during its transmission. (redis tutorial)

Message queuing in redis

Redis can use its own publish and subscribe commands to complete the "message push" and "message pull" functions to achieve message queuing. But a drawback of this approach is that consumers must be consistent online, otherwise there will be consumer omissions.

Message queues generally use a separate cluster for message storage, which can be stored in memory or directly on disk. For example, common: RabbitMQ, kafka, rocketMQ, ActiveMQ, zeromq and so on, they have different features and adopt a variety of different implementations, which are suitable for message task distribution in various scenarios. But their essential function is no different from the java "queue" in the single-instance environment mentioned above: the container that holds the message during its transmission. It's just a transition to a "distributed" environment.

List (essentially a two-way linked list) and zset (ordered set) in redis can be used as containers for "message queues" and a highly available "message queue" can be achieved with a little processing. "lightweight" and "message queuing" implemented with redis have three major advantages:

1. Now redis has been widely used in various systems, and there is no need to introduce other third-party frameworks and api again.

2. And redis is based on memory storage, and the access speed of both producers and consumers is very fast.

3. Use the capacity of the redis cluster, which can be expanded by adding instances.

If the above three requirements are met, a simple "message queue" can be implemented.

Thank you for reading! After reading the above, do you have a general idea of what redis message queues are? I hope the content of the article will be helpful to all of you. If you want to know more about the relevant articles, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.