I am currently swinging between these two
now it is more inclined to redis, because:
redis can achieve the same queuing function as rabbitmq, and the two are tied
redis also has an additional function to cache data
do I understand this correctly
I am currently swinging between these two
now it is more inclined to redis, because:
redis can achieve the same queuing function as rabbitmq, and the two are tied
redis also has an additional function to cache data
do I understand this correctly
in fact, there are some errors in the understanding of the subject.
the development philosophy of redis itself is to make a simple and efficient storage system with functions such as message queue, and does not make more improvements for message queue. For example, message consistency is not well guaranteed, there is no ack mechanism (of course, there are solutions that can be implemented on their own), which specialize in all the things that message queues have.
so when there are few scenarios with message queue-related requirements or when the project size is not very large, it is no problem to go to Redis. As the project becomes larger and larger and the message queue has more and more scenarios to deal with, you will find that it is not as comfortable as the last dedicated message queue.
subject can take a look at the article https://www.zhihu.com/questio. in which the great gods have explained it very clearly.
I was also enlightened when I watched it before, which broke all my doubts.
location is different. RabbitMQ is used to make a high-performance, high-availability message queue. Of course, the list of
Redis can also be a simple queue, but the availability of RabbitMQ on the
message queue, which is mainly used as a cache, is much higher
redis. The author is very ambitious. Look at the stream function of 5.0. that is not a complete message queue.
Previous: CentOS6 install GLIBC_2.14